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/zyrexnn/cybermes/recongit clone --depth 1 https://github.com/Zyrexnn/CybermesWrote 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/commands/zyrexnn/cybermes/recon)<a href="https://agentmods.dev/commands/zyrexnn/cybermes/recon"><img src="https://agentmods.dev/badge/commands/zyrexnn/cybermes/recon.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.03446 |
| Opus 5 | $0.00000 | $0.01723 |
| Sonnet 5 | $0.00000 | $0.00689 |
| Haiku 4.5 | $0.00000 | $0.00345 |
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 3d 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" \ This is a copy
100% identical to recon — 0 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.
How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: recon description: 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
/recon
Run the full recon pipeline on a target and produce a prioritized attack surface.
What This Does
- Enumerates subdomains (Chaos API + subfinder + assetfinder)
- Resolves DNS and finds live hosts (dnsx + httpx with status/title/tech)
- Crawls URLs (katana deep crawl + waybackurls + gau historical)
- Classifies URLs by bug class (gf patterns)
- Runs nuclei for known CVEs and misconfigs
- 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: $CHAOS_API_KEY" \
| 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)"
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.
- 3d ago First seen · 307 lines · 0 tokens per session scan A a63a582f5200
recon is a command published in the GitHub repository Zyrexnn/Cybermes (668 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,446 tokens. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to recon, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
aod.deliver
Close a completed feature with automatic documentation updates and cleanup (Triad-enhanced).
aod.project-plan
Create implementation plan with dual sign-off (PM + Architect) - Streamlined v2.
tachi.architecture
Generate an architecture description for tachi threat modeling input.
aod.roadmap
Scaffold a quarterly roadmap document from completed PRDs with PM sign-off.
aod.update
Apply upstream template updates to this adopter project.
aod.blueprint
Unified project setup & story generation — auto-detects new vs existing projects.