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/recongit 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.01245 |
| Opus 5 | $0.00000 | $0.00622 |
| Sonnet 5 | $0.00000 | $0.00249 |
| Haiku 4.5 | $0.00000 | $0.00125 |
Grade A, and why
recon scanned grade A with 0 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/recon
Run the full recon pipeline on a target. Always invoke the production script directly — do not re-implement the steps inline. The methodology below is reference material; the script is the entry point.
Run This (the only required step)
# Domain (full subdomain enum + crawl + fuzz):
bash tools/recon_engine.sh target.com
# CIDR — skips subdomain enum, runs nmap host sweep:
bash tools/recon_engine.sh 10.0.0.0/24
# Single IP — scope-locked, no subdomain enum:
bash tools/recon_engine.sh 192.0.2.10
# Domain list (programs without wildcard scope) — pre-resolved hosts in a file:
bash tools/recon_engine.sh path/to/scope.txt
# Quick mode (skip amass + reduce ffuf coverage):
bash tools/recon_engine.sh target.com --quick
The script auto-detects target type:
- Path to a readable file → loads it as a host list (one per line,
#comments OK) and skips subdomain enumeration entirely. x.x.x.x/y→ CIDR sweep (max /24, scope-locked).x.x.x.x→ single IP, scope-locked.- Anything else → treated as a domain; full enum runs.
Output lands in recon/<target>/ (or recon/<file-basename>/ for list mode):
recon/<target>/
├── subdomains/all.txt
├── live/urls.txt
├── urls/all.txt
├── candidates/{xss,ssrf,idor,sqli,redirect,lfi}.txt
├── api-endpoints.txt
├── nuclei/findings.txt
└── cicd/summary.txt (if CI/CD workflows detected)
Troubleshooting
"/recon path/to/file.txt still runs subdomain enumeration"
You're on an older revision of this command file where the model re-implemented the pipeline inline and never invoked the production script. Pull latest, or run the script directly:
bash tools/recon_engine.sh path/to/file.txt
You should see [*] Domain-list target — loading <file> (skipping subdomain enum) near the start.
"/recon loops / doesn't actually run anything"
Same root cause as the hunt-loop bug. Run the bash directly:
bash tools/recon_engine.sh target.com
Or in your prompt: "Run bash tools/recon_engine.sh target.com and report the output. Do not re-implement the steps."
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 · 113 lines · 0 tokens per session scan A 1ef45db5fc71
recon is a command published in the GitHub repository Awarexone/Agentic-Bug-Hunter (4,651 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,245 tokens. A static security scan graded it A with 0 findings. 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.