hunt-dispatch

Fingerprints targets and loads the matching red team or WAPT skill set for /hunt.

6|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Wyl-cmd/kxns-cli --skill hunt-dispatch-wyl-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-dispatch
Source: https://github.com/Wyl-cmd/kxns-cli/tree/main/src/kxns_cli/skills/hunt-dispatch
Command: npx skills add https://github.com/Wyl-cmd/kxns-cli --skill hunt-dispatch-wyl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a penetration testing engagement starts, an operator must decide which of dozens of attack skills to load for a given target. Loading everything exhausts the context window, while loading too little misses the platform-specific attack surface. This Skill automates that decision by fingerprinting live hosts and selecting the right skill set based on the engagement mode. ## Core Features & Use Cases - Target Fingerprinting: Runs curl-based header and body probes against every live host, following redirects, and maps signals (Okta, Entra, Next.js, Laravel, Kubernetes, gRPC, and more) to specific platform attack skills. - Mode-Based Skill Loading: Loads the always-on, platform, and hunt-* skill sets for redteam mode, or the full OWASP-oriented hunt-* set for WAPT blackbox/greybox mode, with an 8-skill load budget, tier-based priority, and de-duplication rules. - Greybox Credential Preflight: Validates supplied credentials with a low-cost authenticated probe before running authenticated tests, confirming the session is live, the role is known, and no MFA challenge blocks access. - Use Case: After answering the /hunt mode prompt with "wapt greybox", this Skill fingerprints the target, detects a Next.js front end behind an Okta SSO redirect, loads the matching skills within budget, validates the supplied session cookie, and prints the loaded-skill taxonomy before handing control back to /hunt. ## Quick Start After answering the /hunt mode prompt, invoke hunt-dispatch with your chosen mode such as mode=redteam or mode=wapt box=greybox to fingerprint the target and load the matching attack skills.

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 penetration testing skills to load for a target?

Fingerprint every live host with curl using -L to follow redirects, capturing both headers and body markers like __NEXT_DATA__ or laravel_session. Map each signal to its platform skill, then load matches in tier order up to the 8-skill budget.

What is the difference between redteam and wapt mode in hunt-dispatch?

Redteam mode loads redteam-mindset, IR detection, fingerprint-matched platform skills, and a high-impact hunt-* subset with the redteam report template. WAPT mode loads the full OWASP-oriented hunt-* set with bb-methodology and the report-writing format.

How do I validate greybox credentials before authenticated testing?

Send one authenticated GET to an identity endpoint like /api/me using the session cookie or bearer token. Confirm it returns 200 with the expected role and no MFA challenge before running any authenticated hunt-* tests.

Why does a CDN banner not trigger a platform skill match?

A Cloudflare or Akamai banner fingerprints the edge, not the application, so no platform skill is loaded for it. It is only noted for hunt-cache-poison and hunt-http-smuggling, which the mode set already carries.

What happens when more than 8 platform signals match one target?

Only the highest-tier 8 skills are loaded, ordered from identity/SSO down to protocol-class signals. The remaining matches are listed under a deferred line in the taxonomy so they can be loaded on demand later.