hunt — Claude Code command: what it does, how to install
hunt dispatches vulnerability assessments across Red Team and WAPT workflows with scope boundaries.
MIT ★ 16,193 updated 2026-10-29
/plugin marketplace add elementalsouls/Claude-BugHunter
/plugin install claude-bughunter@elementalsoulsWhat hunt does
The /hunt command acts as a routing controller for application security assessments. It prompts for the engagement track: a high-impact Red Team path focused on exploit chains or a standard WAPT run against OWASP categories in black-box or grey-box mode. It accepts standalone domains, wildcards, or batch files like targets.txt.
Every external HTTP touch is gated behind an enforced /scope check. Optional flags let the runner hook into source code paths via --source-code or activate headless browser tooling with --chrome.
Grey-box credentials remain strictly in transient session memory and never hit persistent logs. Test records stay isolated in a git-ignored targets/<target>/SESSION.md file.
What it helps with
- dispatch target lists into Red Team or OWASP bug hunting workflows
- enforce explicit scope boundaries before initiating outbound network probes
- combine static source code scanning with dynamic target evaluation
- route browser MCP sessions for single-page applications and OAuth flows
Example prompts for the agent
- /hunt target.com
- /hunt *.target.com --chrome
- /hunt targets.txt --vuln-class sqli
How to install hunt
1Plugin marketplace
/plugin marketplace add elementalsouls/Claude-BugHunter/plugin install claude-bughunter@elementalsouls2Manually: put the files in place
.claude/commands/hunt.mdCall it with /hunt. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/hunt.mdCall it with /prompts:hunt. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/hunt.prompt.mdManually: put the files in place
.gemini/commands/hunt.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about hunt
How to install hunt in Claude Code?
Run /plugin marketplace add elementalsouls/Claude-BugHunter followed by /plugin install claude-bughunter@elementalsouls.
What does the hunt command do?
It collects engagement scope, selects the test track, and hands target assets off to specialized hunting skills.
How are test credentials handled in grey box mode?
Credentials exist solely inside runtime memory and are discarded without writing them to disk.
Source text
hunt.md · MIT
---
name: hunt
description: Active vulnerability hunting. Two-track dispatcher — asks Red Team vs WAPT, hands off to hunt-dispatch skill and sibling commands. Usage: /hunt target.com | /hunt *.target.com | /hunt targets.txt [--vuln-class X] [--source-code P] [--chrome]
---
# /hunt
slim two-track dispatcher. one mode question, one branch, delegate.
**engagement frame — state once, then proceed.** invoking `/hunt` asserts the operator holds written
authorization to assess the named scope: a bug-bounty program's in-scope assets, a signed engagement
letter, infrastructure they own, or a practice target. work stays inside that scope — an out-of-scope
host stops the run rather than widening it. the deliverable is a reproducible, remediable finding.
do not prompt for this and do not ask about the SOW. it is an assertion the operator already made by
invoking the command; restating it once keeps the engagement context explicit for the rest of the
session instead of leaving it implied.
## step 0 — parse
```
target.com single target
*.target.com wildcard — /recon <base> first, then hunt each live host
targets.txt multi-target — mode question once, applied per line
--vuln-class <X> skip mode question, load only hunt-<X>
--source-code <p|url> static + dynamic
--chrome browser MCP mode
```
wildcard handler: if `$TARGET` begins with `*.`, strip prefix and invoke `/recon <base>` before continuing.
## step 1 — mode dispatcher
skipped if `--vuln-class` is set.
```
question: "what kind of engagement is this for {target}?"
header: "engagement"
options:
1. Red Team Assessment — critical/high impact, chained findings, client deliverable
2. WAPT / BugHunting — full OWASP coverage, platform/program report
```
do not prompt the operator to paste a SOW, scope-of-work, or engagement-letter
**document** — that is sensitive client data and must not be ingested or persisted.
This is a data-hygiene rule, NOT an authorization bypass: scope is still enforced by
`/scope` (deterministic, deny-wins) and the `triage-validation` 7-Question Gate before
any finding ships. Authorization is assumed to be established out-of-band; the bundle
verifies in-scope, it does not collect proof-of-authorization paperwork.
## step 2a — red team
```
mode: redteam
severity gate: critical / high · medium only if it chains via /chain
report: redteam-report-template
```
invoke `hunt-dispatch` skill with `mode=redteam`. hunt-dispatch fingerprints the target, loads platform skills + always-on (`redteam-mindset`, `mid-engagement-ir-detection`), and prints the taxonomy.
## step 2b — wapt
ask again:
```
question: "black box or grey box?"
header: "test mode"
options:
1. Black Box — no credentials, external perspective
2. Grey Box — test credentials provided (or skip)
```
grey box → prompt `creds (user/pass or token), or "skip":`. creds live in session memory only — never written, never logged. late-bind: if user later says "now grey box with X/Y", capture creds, do NOT re-fire mode question.
```
mode: wapt / {blackbox|greybox}
severity gate: all owasp-relevant
report: report-writing (bugcrowd-reporting if target on bugcrowd)
```
invoke `hunt-dispatch` skill with `mode=wapt box=blackbox|greybox`.
## step 3 — sibling delegation
```
before any HTTP touch → /scope (mandatory pre-flight)
recon empty | wildcard → /recon <target>
5+ live hosts surfaced → /surface (P1/P2/Kill list)
confirmed finding → /chain (A→B table lives here, NOT in /hunt)
before any report → /validate (7-Question Gate)
findings ready → /report (suggest, never auto)
session end → /remember (silent)
```
## step 4 — active testing
hand off to the loaded `hunt-*` skills. each skill has its own probes, payloads, validation. do not duplicate that logic here. on every confirmed finding, invoke `/chain` to check the A→B signal table.
## modes
`--source-code <path|url>` — adds hardcoded-secret grep, route mapping, dangerous-function scan before live testing.
`--chrome` — browser MCP for SPA / OAuth / DOM-XSS / WebSocket / file upload.
`--vuln-class <X>` — load only `hunt-<X>`, skip mode question.
## pacing & isolation
20-min rotation: every 20 min ask "am i making progress?" no → rotate. stop signals: 403 everywhere · 20+ payloads identical response · 5+ preconditions · 30+ min stuck on one endpoint.
one session per target. for `targets.txt`, mode question fires once; findings scoped per-target in hunt memory.
## privacy
never prompt for, log, or echo SOW / scope-of-work / engagement-letter content. never persist grey box credentials to disk. client data lives only in `.gitignore`d `targets/<target>/SESSION.md`.
at session end, invoke `/remember` silently (non-fatal).
© Sachin Sharma · MIT · elementalsouls/Claude-BugHunter