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 skills/hermeticormus/libresecops-claude-code/recon-methodologynpx skills add HermeticOrmus/LibreSecOps-Claude-Code --skill recon-methodologygit 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/skills/hermeticormus/libresecops-claude-code/recon-methodology)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/recon-methodology"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/recon-methodology.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.1 | $0.00000 | $0.02097 |
| Opus 5 | $0.00000 | $0.01048 |
| Sonnet 5 | $0.00000 | $0.00419 |
| Haiku 4.5 | $0.00000 | $0.00210 |
Grade A, and why
recon-methodology 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 6d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recon Methodology
Comprehensive reconnaissance methodology for authorized bug bounty programs covering subdomain enumeration, technology fingerprinting, content discovery, and attack surface mapping.
Knowledge Base
Recon Philosophy
Reconnaissance is the foundation of bug bounty hunting. The depth and quality of your recon directly determines the uniqueness and impact of your findings. Most hunters run the same automated tools against the same targets. The difference is in methodology -- how you process, correlate, and act on recon data.
The key insight: the most interesting targets are the ones nobody else is testing -- forgotten subdomains, old API versions, acquired domains, staging environments, internal tools accidentally exposed. Deep recon reveals these.
Passive Reconnaissance (No Target Interaction)
Certificate Transparency:
# crt.sh - Query CT logs for all certificates issued to a domain
curl -s "https://crt.sh/?q=%.example.com&output=json" | jq -r '.[].name_value' | sort -u
# CertSpotter
curl -s "https://api.certspotter.com/v1/issuances?domain=example.com&include_subdomains=true" | jq -r '.[].dns_names[]' | sort -u
DNS passive sources:
- SecurityTrails API: Historical DNS records, subdomains, associated domains
- VirusTotal: Passive DNS, subdomains, related URLs
- AlienVault OTX: Passive DNS, threat context
- RapidDNS:
https://rapiddns.io/subdomain/example.com - DNSDumpster: Visual DNS mapping
Search engine dorking:
# Subdomain discovery
site:example.com -www
# Exposed files
site:example.com filetype:pdf | filetype:doc | filetype:xls
site:example.com filetype:env | filetype:yml | filetype:config
# Admin panels
site:example.com inurl:admin | inurl:panel | inurl:dashboard
# Error messages (technology disclosure)
site:example.com "error" | "exception" | "stack trace" | "debug"
# Login pages
site:example.com inurl:login | inurl:signin | inurl:auth
# API documentation
site:example.com inurl:api | inurl:swagger | inurl:graphql
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.
- 6d ago First seen · 205 lines · 0 tokens per session scan A 7445eada1366
recon-methodology is a skill 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 2,097 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 skills, from other repositories
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
building-devsecops-pipeline-with-gitlab-ci
Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.
implementing-runtime-application-self-protection
Deploy Runtime Application Self-Protection (RASP) agents to detect and block attacks from within application runtime, covering OpenRASP integration, attack pattern detection, and security policy configuration for Java and Python web applications.
audit-production-readiness
Audit a repository or service for release-blocking bugs, security, data/privacy, AI-agent, supply-chain, operability, and scale risks. Use for deep code audits, threat models, pre-production reviews, vulnerability triage, incidents, defensive investigation, release gates, or evidence-based 10k-to-1M-user readiness.
engineer-production-systems
Design, write, refactor, or optimize production code so it is secure, correct, resource-bounded, observable, and maintainable. Use for full-stack features, APIs, databases, AI/RAG/MCP tools, CPU/RAM/latency work, 10k-to-1M-user planning, or authorized kernel, browser, parser, protocol, and defensive…
best-in-code
Run an adaptive, reusable software-delivery harness across AI models with project management, planning, research, design, frontend, backend, QA, durable scoped memory, capability fallbacks, bounded discovery, and human approval gates. Use when the user invokes Harness or asks for an end-to-end build, review, bug…