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 skills add Orizon-eu/claude-code-pentest --skill recon-dominatorgit clone --depth 1 https://github.com/Orizon-eu/claude-code-pentestWrote 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/orizon-eu/claude-code-pentest/recon-dominator)<a href="https://agentmods.dev/skills/orizon-eu/claude-code-pentest/recon-dominator"><img src="https://agentmods.dev/badge/skills/orizon-eu/claude-code-pentest/recon-dominator/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/skills/orizon-eu/claude-code-pentest/recon-dominator"><img src="https://agentmods.dev/badge/skills/orizon-eu/claude-code-pentest/recon-dominator.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.00096 | $0.01545 |
| Opus 5 | $0.00048 | $0.00772 |
| Sonnet 5 | $0.00019 | $0.00309 |
| Haiku 4.5 | $0.00010 | $0.00154 |
Grade A, and why
recon-dominator scanned grade A with 0 findings 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 9d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recon Dominator
Full-scope reconnaissance orchestrator. From a single domain to a complete attack surface map.
Important
CRITICAL: Only use on domains you have explicit authorization to test. Verify scope before every engagement.
Instructions
Step 1: Scope Validation
Before ANY reconnaissance activity:
- Ask the user to confirm they have written authorization to test the target domain(s)
- Confirm the scope boundaries (wildcard subdomains? specific IPs only? out-of-scope assets?)
- Document the scope in the output
Step 2: Passive Subdomain Enumeration
Run passive enumeration first (no direct contact with target):
python scripts/passive_recon.py --domain {target_domain}
This collects subdomains from:
- Certificate Transparency logs (crt.sh)
- DNS datasets (SecurityTrails, DNSDumpster)
- Search engine results
- Wayback Machine archives
Expected output: JSON list of discovered subdomains with source attribution.
Step 3: Active Subdomain Enumeration
After passive phase, run active enumeration:
python scripts/active_recon.py --domain {target_domain} --wordlist references/subdomains-wordlist.txt
This performs:
- DNS brute-force with common subdomain wordlist
- DNS zone transfer attempts
- Virtual host discovery
- Permutation/alteration scanning (dev-, staging-, api-, etc.)
Step 4: Live Host Detection and Port Scanning
python scripts/port_scanner.py --input {subdomains_file} --top-ports 1000
For each live subdomain:
- HTTP/HTTPS probe (status codes, redirects, titles)
- Top 1000 port scan with service version detection
- Banner grabbing on open ports
- WAF/CDN detection (Cloudflare, Akamai, AWS CloudFront)
Step 5: Technology Fingerprinting
python scripts/tech_fingerprint.py --input {live_hosts_file}
Detect:
- Web server (Apache, Nginx, IIS, etc.)
- Programming language/framework (PHP, Django, Rails, Spring, etc.)
- CMS (WordPress, Drupal, Joomla)
- JavaScript frameworks (React, Angular, Vue)
- Third-party services and integrations
- HTTP security headers (or lack thereof)
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/subdomains-wordlist.txt 1.9 KB
- references/tools-setup.md 1.1 KB
- scripts/active_recon.py 11 KB runs code
- scripts/generate_report.py 9.9 KB runs code
- scripts/google_dorker.py 7.9 KB runs code
- scripts/osint_correlator.py 9.1 KB runs code
- scripts/passive_recon.py 9.2 KB runs code
- scripts/port_scanner.py 10 KB runs code
- scripts/tech_fingerprint.py 8.8 KB runs code
- scripts/wayback_analyzer.py 11 KB runs code
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.
- 9d ago First seen · 199 lines · 96 tokens per session scan A 71a5cff1cd21
recon-dominator is a skill published in the GitHub repository Orizon-eu/claude-code-pentest (25 stars, last pushed 6mo ago), licensed MIT. It adds 96 tokens to every session and 1,545 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
forensics-kit
Digital forensics and incident response toolbox. Load when the operator asks about a pcap, a binary, a memory dump, a suspicious file, malware triage, IOC hunting, or post-incident analysis. Covers network (tshark), binaries (radare2, strings, binwalk, file, exiftool), memory (volatility), and pattern matching (YARA).…
passive-osint
Passive reconnaissance against a target without sending traffic that could alert it. Load when the engagement starts, when you only know a domain/email/username, when scope is unclear, or when you need historical surface area. Covers subdomain enumeration (crt.sh, subfinder), historical archives (wayback), DNS posture…
mobile-pentest
Mobile app pentest for bug bounty (Android APK + iOS IPA) — runtime-first workflow: install app, proxy through Burp/mitmproxy, drive the UI, capture packets, then test the API exactly like a web target; escalate to decompile (apktool/jadx) and Frida/objection only when traffic is SSL-pinned, encrypted, or absent.…
bugcrowd-reporting
Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exact match exists, manual severity override when VRT defaults underrate impact, severity-request paragraph as first body section, OOS-clause rebuttal templates (rate limiting on auth-flow endpoints…
hunt-api-misconfig
Hunt API security misconfiguration — mass assignment, prototype pollution, HTTP verb tampering. Mass assignment: send {isadmin:true, role:admin, verified:true} on profile/account/reset endpoints — server blindly applies. JWT signature/crypto forging (alg:none, key confusion, kid/jku) is owned by hunt-jwt-crypto; this…
hunt-ato
Hunt account takeover taxonomy — 9 distinct paths to ATO, plus chains. Paths: (1) password reset flaws (host-header injection redirects token, predictable/numeric token, Referer leak, no-expiry/reuse), (2) email change without re-auth, (3) OAuth account-link CSRF, (4) MFA bypass (per hunt-mfa-bypass), (5) session…