hunt-dispatch

Fingerprints authorized targets and loads the matching red team or WAPT skill set.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/inventashif/helpful-code-sidekick --skill hunt-dispatch-inventashif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-dispatch
Source: https://github.com/inventashif/helpful-code-sidekick/tree/main/scripts/hackerai/skills/bughunter/hunt-dispatch
Command: npx skills add https://github.com/inventashif/helpful-code-sidekick --skill hunt-dispatch-inventashif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When running an authorized security engagement, choosing which attack-surface skills to load for a given target is error-prone: modern apps return soft-404s that fake findings, hosts run mixed stacks, and loading every matching skill blows the context window. This Skill acts as the dispatcher for the /hunt orchestrator, turning a mode answer (redteam or wapt, blackbox or greybox) into a deterministic, budget-capped skill loadout. ## Core Features & Use Cases - Soft-404 baseline: Records a per-host control (status, byte length, body hash) from bogus paths so no path counts as found unless its response differs from the control. - Fingerprint-driven routing: Maps banner and body markers (Okta, Entra, Next.js, Laravel, Spring Boot, gRPC, Kubernetes, and more) to platform and hunt-* skills, with tier-based priority, an 8-skill load cap, and de-duplication rules. - Mode-specific loadouts and taxonomy print: Loads always-on, platform, and hunt-* sets for redteam or wapt modes, validates greybox credentials with an auth preflight, and emits a deterministic taxonomy block before returning control to /hunt. - Use Case: After confirming an engagement is a greybox WAPT, invoke the dispatcher to baseline each host, validate the supplied session cookie against an identity endpoint, load the full OWASP-relevant hunt-* set, and print the loaded-skills taxonomy. ## Quick Start Run hunt-dispatch with mode=wapt box=greybox after /hunt collects the engagement mode and credentials.

Frequently Asked Questions about hunt-dispatch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose which pentesting skills to load for a target?

Fingerprint every live host with curl following redirects, then map banner and body markers (Okta, __NEXT_DATA__, laravel_session, and similar) to platform and hunt-* skills. Apply the tier priority order and cap platform loads at 8, deferring the rest.

How do I avoid false positives from soft-404 responses?

Record a per-host control by requesting two bogus paths and storing status, byte length, and body hash. Treat any later response matching that triple as a soft 404; only responses differing from the control count as found paths.

Does this skill run attacks against the target directly?

No. It only loads context: it baselines hosts, fingerprints platforms, validates greybox credentials, prints the taxonomy, and returns control to /hunt. Actual probing happens in the loaded hunt-* skills after handoff.

How are greybox credentials validated before authenticated testing?

A single low-cost preflight probes an identity endpoint like /api/me with the session cookie or bearer token. It confirms the session is live (HTTP 200), shows the expected role, and is not stopped at an MFA challenge before any authenticated hunt-* test runs.

What happens when more than eight platform signals match one host?

The loader keeps the highest-tier eight matches (identity, perimeter, cloud, framework, then protocol classes) and lists the dropped skills under a deferred line in the taxonomy so they can be loaded on demand later.