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.
git clone --depth 1 https://github.com/frendysanusi/claude-pentest-skillsWrote 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/frendysanusi/claude-pentest-skills/validate)<a href="https://agentmods.dev/commands/frendysanusi/claude-pentest-skills/validate"><img src="https://agentmods.dev/badge/commands/frendysanusi/claude-pentest-skills/validate.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.00577 |
| Opus 5 | $0.00000 | $0.00289 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
validate 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 8d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 8d ago First seen · 75 lines · 0 tokens per session scan A 891f3bd383ee
validate is a command published in the GitHub repository frendysanusi/claude-pentest-skills (36 stars, last pushed 4mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 577 tokens. 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 commands, from other repositories
selfheal
Thin wrapper (GETSITREP-10) — every check below, and every auto-fix, lives in getsitrep selfheal (src/commands/selfheal.js is the single source of truth for exact behavior and known scope boundaries; this file is a pointer to it, not a second copy of its logic).
debug
Command "debug" from vignesh2027/claude-best-practice, covering /debug — systematic debugging workflow, debugging protocol, phase 1: understand the problem, phase 2: gather evidence and get relevant logs.
refactor
Command "refactor" from vignesh2027/claude-best-practice, covering /refactor — safe refactoring workflow, pre-refactor safety check, refactoring rules, change types (in safe order) and level 1: rename only.
fix-issue
Command "fix-issue" from KhaiTrang1995/claude-code-structure, covering /project:fix-issue – fix issue command, usage, description, shell steps and run tests after fix.
report-fix
Fix issues identified in a project report.
doctor
Check OCR installation and verify all dependencies are available.