Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/awarexone/agentic-bug-hunter/huntgit clone --depth 1 https://github.com/Awarexone/Agentic-Bug-HunterWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.03325 |
| Opus 5 | $0.00000 | $0.01663 |
| Sonnet 5 | $0.00000 | $0.00665 |
| Haiku 4.5 | $0.00000 | $0.00332 |
Grade C, and why
hunt scanned grade C with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Cloud metadata endpointhighServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
curl "https://target.com/api/image?url=http://169.254.169.254/latest/meta-data/iam/security-credentials/" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- DOM-based XSS (invisible to curl probes) How it starts
The opening of the file, as written. The whole thing — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/hunt
Active vulnerability hunting on a target. Always invoke the production script directly — do not re-interpret the methodology below as instructions to execute step-by-step. The methodology is reference material; the script is the entry point.
Run This (the only required step)
# If recon/<target>/ already exists, scan only:
python3 tools/hunt.py --target target.com --scan-only
# If no recon yet, run the full pipeline (recon then scan):
python3 tools/hunt.py --target target.com
# Quick mode (fewer checks, faster):
python3 tools/hunt.py --target target.com --quick
That's it. The script:
- Reads
recon/<target>/(subdomains, live hosts, URLs, gf-classified candidates). - Runs
tools/vuln_scanner.sh recon/<target>/— XSS (dalfox), SQLi (linear-scaling verifier), SSTI math-canary probes, race conditions, RCE PoC, MFA/SAML checks. - Writes results to
findings/<target>/with asummary.txt.
Output you should see (not a loop):
██████ ██████ ██ ██ ██ ██ ███ █ ███████
██ ██ ██ ██ ██ ██ ██ ██ ████ █ ███
██████ ██████ ███████ ██ ██ ██ ██ █ ███
██████ ██████ ███████ ██ ██ ██ ███ ███
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███
██████ ██████ ██ ██ ███████ ██ ██ ███
+ Recon. Hunt. Validate. Report. +
┌──────────────────────────────────────────────────────┐
│ Target target.com │
│ Mode full │
│ Output recon/target.com/ │
│ Auth session loaded │
└──────────────────────────────────────────────────────┘
● local Ready type /hunt to begin
bbhunt v4.3
[*] Running vulnerability scanner on target.com...
[+] XSS pipeline: N candidates
[+] SQLi verifier: ...
[+] SSTI canary: ...
[✓] HUNT COMPLETE — Summary Dashboard
Pass --no-banner for piped / CI output. Pipe through python3 tools/dashboard.py --tail --kind scan --target target.com for a live phase-by-phase progress dashboard instead of streaming logs.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 343 lines · 0 tokens per session scan C d85ea95eadf8
hunt is a command published in the GitHub repository Awarexone/Agentic-Bug-Hunter (4,651 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,325 tokens. A static security scan graded it C with 2 findings (cloud metadata endpoint, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
recon
Run full recon pipeline on a target — subdomain enum (Chaos API + subfinder), live host discovery (dnsx + httpx), URL crawl (katana + waybackurls + gau), gf pattern classification, nuclei scan. Outputs to recon/ / directory. Usage: /recon target.com.
hunt
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].
token-scan
Meme coin and token security scan — checks for rug pull vectors (hidden mint, honeypot, fee manipulation, LP lock bypass, authority retention, bonding curve exploits, fake renounce, sandwich amplification). Manual 8-class grep audit (with an optional automated scanner if present). Usage: /token-scan [--chain solana].
autopilot
Run autonomous hunt loop on a target — scope check → recon → rank surface → hunt → validate → report with configurable checkpoints. Usage: /autopilot target.com [--paranoid|--normal|--yolo].
triage
Quick 7-Question Gate triage on a finding before writing a report. Kills N/A submissions before they happen. Faster than /validate — for quick go/no-go decisions. Usage: /triage.
validate
Validate a finding — runs 7-Question Gate + 4-gate checklist. Kills weak findings before report writing. Prevents N/A submissions that hurt validity ratio. Usage: /validate.