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-kali)<a href="https://agentmods.dev/commands/stickman230/claude-pentest/pentest-kali"><img src="https://agentmods.dev/badge/commands/stickman230/claude-pentest/pentest-kali/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-kali"><img src="https://agentmods.dev/badge/commands/stickman230/claude-pentest/pentest-kali.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.00043 | $0.01802 |
| Opus 5 | $0.00022 | $0.00901 |
| Sonnet 5 | $0.00009 | $0.00360 |
| Haiku 4.5 | $0.00004 | $0.00180 |
Grade A, and why
pentest-kali 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 10d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output the following banner verbatim:
============================================================
[MKS — KALI TOOL CONNECTION]
============================================================
Step 1 — Collect MKS Server URL
Use AskUserQuestion to ask:
"MKS Server URL — What is the URL of your Metasploit-Kali Server? (e.g., http://192.168.1.10:5000 or http://kali:5000)"
Store the answer as mks_url. Strip any trailing slash from the value.
Step 2 — Verify Connectivity
Run Bash:
curl -s -m 10 {mks_url}/health
Store the full response body as health_response.
If the Bash command fails (non-zero exit code), or if health_response is empty, output this block verbatim and stop:
============================================================
CONNECTION FAILED
============================================================
Could not reach MKS server at {mks_url}.
Possible causes:
- Server is not running (start with: python server.py)
- URL or port is incorrect
- Firewall is blocking the connection
- SSH tunnel is not established
Run /pentest:pentest-kali again once the server is reachable.
============================================================
If health_response is non-empty, parse it as JSON. If the status field is not "healthy", output:
============================================================
SERVER UNHEALTHY
============================================================
MKS server responded but reported status: {status}
Message: {message}
The server is running but essential tools may be missing.
Check that nmap, gobuster, dirb, and nikto are installed on the Kali host.
============================================================
Then stop.
Step 3 — Parse Tool Availability
From the parsed health_response, extract the reported booleans:
nmap_ok= value oftools_status.nmap(true/false, default false if missing)gobuster_ok= value oftools_status.gobusterdirb_ok= value oftools_status.dirbnikto_ok= value oftools_status.nikto
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.
- 10d ago First seen · 211 lines · 43 tokens per session scan A 29f0917e3b6e
pentest-kali is a command published in the GitHub repository Stickman230/claude-pentest (100 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 1,802 once invoked, about $0.0002 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.