hunt-dispatch is a skill for Claude that loads the correct skill set once a /hunt engagement has an authorized scope and a mode answer (red team or web application pentest, blackbox or greybox). It runs as the choke point every /hunt session passes through before any individual hunt-* skill loads, and the /hunt command itself is the only intended caller.
The skill opens with a mandatory soft-404 baseline that every host must clear before any path is probed, because many modern front ends return HTTP 200 for paths that do not exist and a status code alone proves nothing. It then fingerprints live hosts, maps the signals it finds to the matching platform or hunt-* skills under a tiered load budget, prints a deterministic taxonomy of what was loaded, and states strict scope-inheritance rules for any work handed to a subagent. It is for engagements where written authorization for the named scope has already been established.
What You Get
- A mandatory soft-404 baseline step that records status, byte length and body hash per host before any path is treated as a real finding
- A fingerprint-to-skill mapping table covering identity providers, enterprise appliances, cloud markers, and web framework signals
- A tiered load-budget system that caps platform-skill loading at eight and defers any further matches to a named list for later use
- Fixed skill-set menus for mode=redteam and mode=wapt, each ending in the matching report-format skill
- An authenticated-testing preflight that validates greybox credentials before fanning out across the authenticated hunt-* set, and explicit subagent scope-inheritance rules including a deny-before-allow verb list
Common Use Cases
- Fingerprinting a set of live hosts in a /hunt engagement and determining which enterprise platform or framework skills to load
- Establishing a soft-404 baseline for a CDN-fronted or SPA target before treating any discovered path as a real finding
- Passing explicit, data-formatted scope boundaries and a deny-before-allow verb list to a subagent before delegating part of an authorized engagement
What Makes It Unique
The skill functions purely as orchestration infrastructure for the bundle, routing to the hunting skills that do the actual class-specific work. Its subagent-scope section carries lessons from a real engagement where a subagent told to stay read-only still created a live production record and wrote to an out-of-scope bucket: scope passed as data, a deny list of action verbs checked before any allow list, and discovered hosts treated as out of scope until the operator says otherwise.
Under The Hood
The skill is a single SKILL.md of guidance with no bundled scripts. Following it, the agent sends HTTP requests to establish a soft-404 baseline and to fingerprint live hosts, reading response headers and body content for platform and framework markers, then invokes other skills by name through the Skill tool based on what it found. It reads from and may create files under a recon/ working directory for per-host results. Use it only within an engagement scope that has already been authorized.