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/hermeticormus/libresecops-claude-code/recon-plangit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/hermeticormus/libresecops-claude-code/recon-plan)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/recon-plan"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/recon-plan.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.01329 |
| Opus 5 | $0.00000 | $0.00665 |
| Sonnet 5 | $0.00000 | $0.00266 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
recon-plan 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 4d 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://crt.sh/?q=%.example.com&output=json" | jq -r '.[].name_value' | sort -u How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/recon-plan
Generate a structured reconnaissance plan for an authorized bug bounty target, with passive and active recon phases, tool recommendations, and prioritized attack surface mapping.
Trigger
Use at the start of a bug bounty engagement after reviewing the program scope. Appropriate when:
- Beginning testing on a new bug bounty program
- Expanding recon on an existing target after initial testing
- Planning recon for a specific asset type (API, mobile, cloud)
- Refreshing recon on a target with updated scope
Input
- Program name and platform: Where the program is hosted (HackerOne, Bugcrowd, etc.)
- Scope: In-scope domains, applications, IP ranges, and mobile apps
- Out of scope: Explicitly excluded targets and testing techniques
- Program rules: Key rules affecting methodology (rate limits, no automated scanning, etc.)
- Your skills and tools: What testing capabilities you have (Burp Pro, mobile testing setup, cloud experience)
- Previous findings (optional): Known vulnerabilities or areas already tested
Process
-
Scope analysis -- Parse the scope to identify all testable assets and explicit boundaries. Map wildcard scopes (*.example.com) vs specific assets (app.example.com).
-
Passive reconnaissance (no direct target interaction):
Subdomain enumeration:
- Certificate Transparency logs:
crt.sh,certspotter - DNS datasets: SecurityTrails, DNSDumpster, RapidDNS
- Search engines: Google dorks (
site:example.com), Bing, DuckDuckGo - GitHub/GitLab code search: Subdomains, API keys, internal URLs
- Wayback Machine: Historical subdomains, removed pages, old API endpoints
- Passive DNS: PassiveTotal, VirusTotal, AlienVault OTX
Technology intelligence:
- Shodan/Censys: Open ports, services, certificates, technologies
- BuiltWith/Wappalyzer data: Technology stack information
- Job postings: Technologies mentioned in hiring (reveals internal stack)
Data exposure:
- GitHub/GitLab: Code repositories, leaked credentials, configuration files
- Pastebin/paste sites: Leaked data, credentials, configuration
- Google dorking: Exposed files, admin panels, error messages
- Cloud storage: S3 buckets, Azure Blobs, GCP Storage naming patterns
- Certificate Transparency 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.
- 4d ago First seen · 146 lines · 0 tokens per session scan A fc8b43cc4f14
recon-plan is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,329 tokens. 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-31.
Other commands, from other repositories
tachi.architecture
Generate an architecture description for tachi threat modeling input.
aod.blueprint
Unified project setup & story generation — auto-detects new vs existing projects.
sicario.assess
Assess the repository against SicarioSpec guardrails.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.