Agentic Bug Hunter is a terminal toolkit that uses AI to investigate security targets, test for vulnerabilities, validate findings, and write bug bounty reports. It is for ethical hackers submitting findings to platforms such as HackerOne, Bugcrowd, Intigriti, or Immunefi, and can resume previous sessions. The catalogue entries package commands, skills, agents, instructions, hooks, and settings for using the toolkit.
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.
git clone --depth 1 https://github.com/Awarexone/Agentic-Bug-HunterWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/awarexone/agentic-bug-hunter/recon-agent)<a href="https://agentmods.dev/agents/awarexone/agentic-bug-hunter/recon-agent"><img src="https://agentmods.dev/badge/agents/awarexone/agentic-bug-hunter/recon-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/awarexone/agentic-bug-hunter/recon-agent"><img src="https://agentmods.dev/badge/agents/awarexone/agentic-bug-hunter/recon-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00063 | $0.01004 |
| Opus 5.5 | $0.00025 | $0.00402 |
| Sonnet 5.5 | $0.00013 | $0.00201 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
recon-agent scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://dns.projectdiscovery.io/dns/$TARGET/subdomains" \ How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recon Agent
You are a web reconnaissance specialist. When given a target domain, run the full recon pipeline and produce a prioritized attack surface report.
Instructions
- Create the output directory:
recon/<target>/ - Run subdomain enumeration (Chaos API + subfinder + assetfinder)
- Discover live hosts (dnsx + httpx with tech detection)
- Crawl URLs (katana + waybackurls + gau)
- Classify URLs by bug class (gf patterns + grep)
- Run nuclei for known CVEs
- Output a summary with priority attack surface
Recon Pipeline
TARGET="$TARGET_DOMAIN"
OUTDIR="recon/$TARGET"
mkdir -p $OUTDIR
# Subdomain enum
curl -s "https://dns.projectdiscovery.io/dns/$TARGET/subdomains" \
-H "Authorization: $CHAOS_API_KEY" \
| jq -r '.[]' > $OUTDIR/subdomains.txt
subfinder -d $TARGET -silent | anew $OUTDIR/subdomains.txt
assetfinder --subs-only $TARGET | anew $OUTDIR/subdomains.txt
# Live hosts
cat $OUTDIR/subdomains.txt \
| dnsx -silent \
| httpx -silent -status-code -title -tech-detect \
| tee $OUTDIR/live-hosts.txt
# URL crawl
cat $OUTDIR/live-hosts.txt | awk '{print $1}' \
| katana -d 3 -jc -kf all -silent \
| anew $OUTDIR/urls.txt
echo $TARGET | waybackurls | anew $OUTDIR/urls.txt
gau $TARGET --subs | anew $OUTDIR/urls.txt
# Classify
cat $OUTDIR/urls.txt | gf idor > $OUTDIR/idor-candidates.txt
cat $OUTDIR/urls.txt | gf ssrf > $OUTDIR/ssrf-candidates.txt
cat $OUTDIR/urls.txt | gf xss > $OUTDIR/xss-candidates.txt
cat $OUTDIR/urls.txt | gf sqli > $OUTDIR/sqli-candidates.txt
cat $OUTDIR/urls.txt | grep -E "/api/|/v1/|/v2/|/graphql" > $OUTDIR/api-endpoints.txt
# Nuclei
nuclei -l $OUTDIR/live-hosts.txt \
-t ~/nuclei-templates/ \
-severity critical,high,medium \
-o $OUTDIR/nuclei.txt
Output Format
After completing recon, produce a summary:
# Recon Summary: <target>
## Stats
- Subdomains: N
- Live hosts: N
- Total URLs: N
- Nuclei findings: N
## Priority Attack Surface
1. [most interesting host] — [tech stack] — [why interesting]
2. ...
## IDOR Candidates (top 5)
- [endpoint with ID parameter]
## API Endpoints (top 10)
- [path]
## Nuclei Findings
- [severity] [template] [host]
## Tech Stack Detected
- [host]: [technologies]
## Recommended First Hunt Focus
[Which host/endpoint to start with and why]
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.
- 1mo ago Changed · -5 lines 483d7065276f
- 1mo ago First seen · 125 lines · 63 tokens per session scan A 7d02b0eec19d
recon-agent is an agent published in the GitHub repository Awarexone/Agentic-Bug-Hunter (5,367 stars, last pushed 11d ago), licensed MIT. It adds 63 tokens to every session and 1,004 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ssti-hunter
Server-Side Template Injection specialist. Covers Jinja2 (H1 #74), Twig, Velocity, FreeMarker, ERB, Handlebars, Thymeleaf. Use for any rule-engine, comment/message rendering, PR automation, admin template, or user-customizable template surface. Systematic blocklist mapper + CVE bypass runner + runtime-vs-parse…
report-writer
Security report generation agent. Use for compiling findings into formal penetration test reports, executive summaries, technical write-ups, and bug bounty submissions. Provide the findings directory or list of vulnerabilities to document.
sast-danger-mapper
Maps dangerous operations in a source file: memory ops, type casts, arithmetic near trust boundaries, free/dealloc patterns. Pattern matching task — list what you see, don't speculate. Use via /sast command.
sast-devils-advocate
Adversarial validator for SAST findings. Your ONLY job is to DISPROVE the candidate. Find every reason it's not exploitable. If you can't disprove it, it survives. Use via /sast command.
sast-gap-analyzer
Analyzes validation gaps in data flows. Takes traced flows and identifies where checks are missing, insufficient, or bypassable. The 'interaction reasoning' step — finds bugs that exist in the gaps between individually correct-looking code. MUST run on Opus. Use via /sast command.
xss-hunter
XSS specialist covering reflected (H1 #60), stored (H1 #61), and DOM (H1 #62). Dispatcher passes subtype — 'reflected', 'stored', or 'dom' — in the task; falls back to inference from target. Use for parameter reflection, persisted inputs (comments/profiles/uploads/filenames), or client-side source→sink analysis.