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-opsec-evidencegit 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-opsec-evidence)<a href="https://agentmods.dev/skills/fatihkan/badi/pentest-opsec-evidence"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/pentest-opsec-evidence/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-opsec-evidence"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/pentest-opsec-evidence.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 77 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.00065 | $0.01531 |
| Opus 5 | $0.00032 | $0.00766 |
| Sonnet 5 | $0.00013 | $0.00306 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade A, and why
pentest-opsec-evidence 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 -A "Mozilla/5.0 (compatible)" --resolve ... How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pentest-opsec-evidence
Operator OPSEC + engagement evidence handling. Minimizing the operator's footprint on the target during a pentest + storing evidence at legal grade.
Triggers
- "assess OPSEC"
- "hide source IP"
- "burner infrastructure"
- "fingerprint hygiene"
- "evidence chain of custody"
- "log retention policy"
Operator Identity Hygiene
Source IP Design
1. Burner cloud VM (AWS / DO / Linode)
- Account: pentest-firm name, real name (do not hide the legal account)
- VM: single engagement, shut down at the end
- Region: pick a region the client can observe
2. Residential proxy (selective use)
- Use without legal authorization is wrong (even Tor carries attribution potential)
- For testing within a bug bounty / authorized engagement
3. Bastion + jump host
- Operator <-> Bastion (own) <-> Cloud VM <-> target
- Bastion log: timestamp + command + operator
Browser/HTTP Fingerprint Hygiene
# Burp / proxy config
- User-Agent: realistic, version-current
- Accept-Language: target locale
- JA3 fingerprint: common browser (Chrome 119 default)
# Tool customization
nmap --max-rate 100 --randomize-hosts
curl -A "Mozilla/5.0 (compatible)" --resolve ...
DNS / SNI Hygiene
# DNS over HTTPS (DoH)
# When making DNS queries toward the target, use 1.1.1.1 DoH instead of your own ISP DNS
# SNI: cloudfront / cloudflare cover behind
# (for authorized use only — within a legal framework)
Tooling Footprint
| Tool | Default Footprint | Stealthy Alternative |
|---|---|---|
| nmap (default) | -sC -sV LOUD | -sT -sV --top-ports 100 --max-rate 100 |
| sqlmap (default) | Many requests, banner | --random-agent --delay 2 --threads 1 |
| BloodHound (default) | Mass LDAP | --throttle 30 --jitter 20 |
| ffuf | 1000 req/s | -t 5 -p 1 |
| nuclei | All templates | -tags sqli,xss only |
Burner Infrastructure
Per engagement:
1. Set up a VM (cloud / your own VPS)
2. Separate SSH key pair (engagement-specific)
3. Tooling stack install (Kali Light / Parrot)
4. Engagement end: snapshot + destroy
5. Snapshot: encrypted (BitLocker / VeraCrypt) cold storage
Persistent:
- Bug bounty researcher: dedicated workstation (1)
- Pentest firm: per-customer VM template
- Red team operator: 3 tiers (recon/exploit/post-ex isolated)
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 · 169 lines · 65 tokens per session scan A d0804f89c915
pentest-opsec-evidence is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed 4d ago), licensed MIT. It adds 65 tokens to every session and 1,531 once invoked, about $0.0003 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…
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.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
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.