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 fatihkan/badi --skill pentest-recongit clone --depth 1 https://github.com/fatihkan/badiWrote 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/fatihkan/badi/pentest-recon)<a href="https://agentmods.dev/skills/fatihkan/badi/pentest-recon"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/pentest-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.
<a href="https://agentmods.dev/skills/fatihkan/badi/pentest-recon"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/pentest-recon.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high YARA Match · line 3 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
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.00083 | $0.01139 |
| Opus 5 | $0.00042 | $0.00570 |
| Sonnet 5 | $0.00017 | $0.00228 |
| Haiku 4.5 | $0.00008 | $0.00114 |
Grade A, and why
pentest-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 for crt.sh: 'https://crt.sh/?q=%25.example.com&output=json' How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pentest-recon
Recon output analysis + attack-surface prioritization + next-step suggestions. Advisory mode — the user pastes output, the skill analyzes it. Active command composing requires a scope declaration.
Triggers
- "nmap output" / "review the scan result"
- "Nessus report"
- "I ran a subdomain enum"
- "where is the attack surface"
- "which target is the priority"
- "BloodHound graph analysis"
- "let's do OSINT"
Input Types
| Input | Skill Behavior |
|---|---|
| Nmap XML/text output | Port + service + version + script output parse, CVE lookup suggestion |
| Nessus / OpenVAS report | Severity + CVSS prioritize, critical findings list |
| Nikto output | Web vulnerability filtering, false positives weeded out |
| BloodHound JSON | Find high-value target paths, attack path prioritization |
| Masscan/Naabu output | Open-port list -> service enum suggestion |
| WHOIS / certificate transparency | Subdomain expansion, additional domain discovery |
Output Template
## Recon Analysis — <target>
### Detection
- 3 open ports: 22/SSH, 80/HTTP, 443/HTTPS
- HTTP: nginx 1.18.0 (CVE-2021-23017)
- HTTPS: Self-signed cert, expired 2024-03-15
- SSH: OpenSSH 7.6p1 (CVE-2018-15473)
### Prioritization
1. [HIGH] CVE-2021-23017 — nginx DNS resolver — exploitable, public PoC available
2. [MEDIUM] OpenSSH user enum (CVE-2018-15473) — username discovery
3. [LOW] Cert expired — config issue, no exploitation value
### Next Step (suggested)
- Active: `nikto -h <target>` (MODERATE OPSEC)
- Passive: SecurityTrails / Censys additional subdomains (QUIET)
- Targeted: nginx version-specific exploit-db search
### Skipped Areas
- UDP scan not done (53, 161 standard practice)
- Vhost discovery skipped
Active Command Composing (Scope Required)
If the user grants scope approval, the skill can suggest the following commands (with examples):
# QUIET — passive subdomain enum
subfinder -d example.com -silent
# MODERATE — TCP service scan, rate-limited
nmap -sT -sV --top-ports 1000 --max-rate 100 -oA scan_example_$(date +%Y%m%d_%H%M%S) <target>
# MODERATE — HTTP fingerprint
httpx -l hosts.txt -title -tech-detect -status-code -o httpx-results.txt
# QUIET — Cert transparency
curl for crt.sh: 'https://crt.sh/?q=%25.example.com&output=json'
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 · 118 lines · 83 tokens per session scan A 4f4e336cff26
pentest-recon is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed 2d ago), licensed MIT. It adds 83 tokens to every session and 1,139 once invoked, about $0.0004 per session on Opus 5. 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-09-06.
Other skills, from other repositories
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.