recon

recon is a command for Claude Code from Mikacr1138/claude-bug-bounty. It costs 0 tokens per session (1,189 once invoked), scanned A, a copy of recon, MIT.

A command that runs a full public-surface discovery process for a domain. It collects subdomains, checks live hosts, crawls current and historical URLs, groups URLs by likely bug type, and scans for known issues.

In plain words
What is it for?
Use it with a domain to discover hosts and endpoints, focus the search on areas such as APIs or authentication, or run a faster scan without historical URLs.
Why use it?
It saves the repeated setup work involved in building an initial map of a target and produces a prioritized attack-surface summary.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: positional $N argument.

Good fit Use it with a domain to discover hosts and endpoints, focus the search on areas such as APIs or authentication, or run a faster scan without historical URLs.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/mikacr1138/claude-bug-bounty/recon
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Mikacr1138/claude-bug-bounty

Made for: Claude Code.

Wrote 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.

agentmods badge for recon

README.md
[![agentmods](https://agentmods.dev/badge/commands/mikacr1138/claude-bug-bounty/recon/github.svg)](https://agentmods.dev/commands/mikacr1138/claude-bug-bounty/recon)
Your own site
<a href="https://agentmods.dev/commands/mikacr1138/claude-bug-bounty/recon"><img src="https://agentmods.dev/badge/commands/mikacr1138/claude-bug-bounty/recon/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.

agentmods 80×15 button for recon

Your own site · 80×15
<a href="https://agentmods.dev/commands/mikacr1138/claude-bug-bounty/recon"><img src="https://agentmods.dev/badge/commands/mikacr1138/claude-bug-bounty/recon.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,189 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01189
Opus 5 $0.00000 $0.00594
Sonnet 5 $0.00000 $0.00238
Haiku 4.5 $0.00000 $0.00119

Measured 10d ago against content hash f778d6d5d967, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

recon 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 10d 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" \
Origin

This is a copy

91% identical to recon — 197 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/recon.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 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 and produce a prioritized attack surface.

What This Does

  1. Enumerates subdomains (Chaos API + subfinder + assetfinder)
  2. Resolves DNS and finds live hosts (dnsx + httpx with status/title/tech)
  3. Crawls URLs (katana deep crawl + waybackurls + gau historical)
  4. Classifies URLs by bug class (gf patterns)
  5. Runs nuclei for known CVEs and misconfigs
  6. Outputs prioritized attack surface summary

Usage

/recon target.com

Or with specific focus:

/recon target.com --focus api
/recon target.com --focus auth
/recon target.com --fast     (skip historical URLs)

Steps

Step 1: Subdomain Enumeration

TARGET="$1"
mkdir -p recon/$TARGET

# Chaos API (ProjectDiscovery — most comprehensive)
curl -s "https://dns.projectdiscovery.io/dns/$TARGET/subdomains" \
  -H "Authorization: 15e77cfb-2300-426a-b8c3-fbfbf0ab17d4" \
  | jq -r '.[]' > recon/$TARGET/subdomains.txt

# subfinder + assetfinder
subfinder -d $TARGET -silent | anew recon/$TARGET/subdomains.txt
assetfinder --subs-only $TARGET | anew recon/$TARGET/subdomains.txt

echo "[+] Subdomains: $(wc -l < recon/$TARGET/subdomains.txt)"

Step 2: Live Host Discovery

# DNS resolve + HTTP probe with tech detection
cat recon/$TARGET/subdomains.txt \
  | dnsx -silent \
  | httpx -silent -status-code -title -tech-detect \
  | tee recon/$TARGET/live-hosts.txt

echo "[+] Live hosts: $(wc -l < recon/$TARGET/live-hosts.txt)"

Step 3: URL Crawl

# Active crawl
cat recon/$TARGET/live-hosts.txt | awk '{print $1}' \
  | katana -d 3 -jc -kf all -silent \
  | anew recon/$TARGET/urls.txt

# Historical URLs
echo $TARGET | waybackurls | anew recon/$TARGET/urls.txt
gau $TARGET --subs | anew recon/$TARGET/urls.txt

echo "[+] Total URLs: $(wc -l < recon/$TARGET/urls.txt)"

Step 4: Classify URLs

# Bug class classification
cat recon/$TARGET/urls.txt | gf xss       > recon/$TARGET/xss-candidates.txt
cat recon/$TARGET/urls.txt | gf ssrf      > recon/$TARGET/ssrf-candidates.txt
cat recon/$TARGET/urls.txt | gf idor      > recon/$TARGET/idor-candidates.txt
cat recon/$TARGET/urls.txt | gf sqli      > recon/$TARGET/sqli-candidates.txt
cat recon/$TARGET/urls.txt | gf redirect  > recon/$TARGET/redirect-candidates.txt
cat recon/$TARGET/urls.txt | gf lfi       > recon/$TARGET/lfi-candidates.txt

# API endpoints
cat recon/$TARGET/urls.txt | grep -E "/api/|/v1/|/v2/|/graphql|/rest/" \
  > recon/$TARGET/api-endpoints.txt

echo "[+] IDOR candidates: $(wc -l < recon/$TARGET/idor-candidates.txt)"
echo "[+] SSRF candidates: $(wc -l < recon/$TARGET/ssrf-candidates.txt)"
echo "[+] API endpoints:   $(wc -l < recon/$TARGET/api-endpoints.txt)"

Read the full file on GitHub · 140 lines

Changes

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.

  1. 10d ago First seen · 140 lines · 0 tokens per session scan A f778d6d5d967

Subscribe to this mod's changes

recon is a command published in the GitHub repository Mikacr1138/claude-bug-bounty (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,189 tokens. A static security scan graded it A with 1 finding (makes network calls). It is 91% identical to recon, differing in 197 lines, and is treated as a copy.