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/Stickman230/claude-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/commands/stickman230/claude-pentest/pentest)<a href="https://agentmods.dev/commands/stickman230/claude-pentest/pentest"><img src="https://agentmods.dev/badge/commands/stickman230/claude-pentest/pentest/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/commands/stickman230/claude-pentest/pentest"><img src="https://agentmods.dev/badge/commands/stickman230/claude-pentest/pentest.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.00058 | $0.06130 |
| Opus 5 | $0.00029 | $0.03065 |
| Sonnet 5 | $0.00012 | $0.01226 |
| Haiku 4.5 | $0.00006 | $0.00613 |
Grade A, and why
pentest 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -m 10 "{mks_url}/health" How it starts
The opening of the file, as written. The whole thing — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output the following ASCII art banner verbatim:
======================================================
| |
| ____ _____ _ _ _____ _____ ____ _____ |
| | _ \| ____| \ | |_ _| ____/ ___|_ _| |
| | |_) | _| | \| | | | | _| \___ \ | | |
| | __/| |___| |\ | | | | |___ ___) || | |
| |_| |_____|_| \_| |_| |_____|____/ |_| |
| |
| M O D E A C T I V A T E D |
| |
======================================================
root@claude:~# [INITIALIZING PENTEST ENVIRONMENT...]
root@claude:~# [READY]
Step 1 — Isolation
Use AskUserQuestion to ask the user:
"Do you want to isolate this session to the pentest plugin only? (Recommended — prevents other plugins interfering with your engagement)"
Present exactly these two options:
- "Yes — isolate me (recommended)"
- "No — keep all plugins active"
If the user selects "Yes — isolate me (recommended)", output the following instruction block verbatim into the conversation:
============================================================
[PENTEST MODE — ISOLATION ACTIVE]
For this session, you MUST operate under these constraints:
- Only invoke agents from the pentest plugin (agents/ directory)
- Only mount skills from the pentest plugin (skills/ directory)
- Ignore agents and skills from all other plugins
- Do not switch to general-purpose tools or non-pentest workflows
- This constraint is active until /pentest:pentest-exit is run or /clear resets the session
============================================================
If the user selects "No — keep all plugins active", output:
Session running with all plugins active. You can still use /pentest:pentest-exit to close the engagement.
Step 2 — Scope Check
Try to Read .pentest-scope.json.
If the file exists and is valid JSON, extract target, engagement, out_of_scope, auth, timing, thoroughness, and output_formats (an array; default to [] if absent). For backward compatibility with older scope files: if timing is absent but a legacy window field is present, use window as timing. Output this block with real values:
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 · 454 lines · 0 tokens per session scan A 33f4c7e426e5
pentest is a command published in the GitHub repository Stickman230/claude-pentest (100 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 6,130 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-08-30.
Other commands, from other repositories
unpack
Detect and remove binary packing/protection.
dashboard
Show running scans, system health, and engagement status.
apiscan
API security audit — REST, GraphQL, JWT analysis, parameter discovery.
payload
AI-powered payload generation for XSS, SQLi, LFI, command injection, and more.
recon
Full reconnaissance workflow — subdomain enum, tech detection, WAF fingerprinting, crawling.
bruteforce
Password brute force and hash cracking against target services.