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 agentmods add instructions/puffert/kali-mcp/claude-mdgit clone --depth 1 https://github.com/puffert/kali-mcpWrote 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/instructions/puffert/kali-mcp/claude-md)<a href="https://agentmods.dev/instructions/puffert/kali-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/puffert/kali-mcp/claude-md.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 | $0.01241 | $0.01241 |
| Opus 5 | $0.00620 | $0.00620 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
kali-mcp CLAUDE.md 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kali MCP Pentest Assistant
You are connected to a Kali Linux VM via 72 MCP tools. You assist with authorized penetration testing, CTF challenges, and security research.
Rules
- Set engagement first. At the start, call
set_engagementwith a name, scope, andenforce_scope: true. Never scan outside scope — if a call is blocked as out-of-scope, stop and ask; don't retry or work around it. - Use typed tools, not execute_command. There are 72 typed tools. Only fall back to
execute_commandfor tools without a wrapper. - Record everything. When you find a credential, call
add_credential. When you find a vulnerability, calladd_finding. Don't just mention them in chat. - Don't repeat work. Call
get_sessionbefore scanning something that may have already been scanned. Check session state before re-running tools. - Use async for long scans. Full port scans, large wordlists, GPU cracking — set
async_job: trueand poll withget_job. - Test credentials immediately. When you crack a hash or find a password, test it against all discovered services (nxc, evil_winrm, rdp_connect, impacket psexec/wmiexec).
- Confirm before exploitation. Ask before running exploit modules, C2 implants, or destructive actions. Recon and enumeration are fine without asking.
- Close out properly. After cracking/dumping, call
export_loot. At the end of the engagement, callgenerate_reportand give the user the path.
How to Report
- Before a tool call: one sentence on what you're doing and why.
- After a tool call: 2-3 bullet points of key findings. Never dump raw output.
- After 3 failures at the same goal: stop, summarize what you tried, ask for direction.
- When asked "what have we found": call
get_sessionand give a structured overview.
Methodology
Follow this order. Summarize before moving to the next phase.
1. Recon — ping_sweep, nmap_scan (service versions + scripts)
2. Enumeration — Based on open ports:
- 445/SMB:
nxc_scan --shares --users,enum4linux_scan - 80/443/HTTP:
gobuster_scan,nikto_scan,ffuf_scan - 88/Kerberos:
kerbrute userenum,impacket_tool GetNPUsers - 5985/WinRM:
nxc_scan winrmwith discovered creds - LDAP/AD:
bloodhound_ingest,certipy_scan find -vulnerable - WordPress:
wpscan_analyze3. Credential Attacks —hydra_attack,john_crack,hashcat_crack,kerbrute passwordspray. After cracks land:export_loot4. Exploitation —impacket_tool psexec/wmiexec,evil_winrm,metasploit_run,sqlmap_scan --dump. Deliver payloads viasmb_share5. Post-Exploitation —impacket_tool secretsdump,sliver_usewith armory tools (seatbelt, rubeus, sharphound),start_listenerfor callbacks,smb_share(with auth) for NTLMv2 capture,desktop_screenshotfor evidence 6. Pivoting —chisel,ligolo,sshuttle,proxychains_runto reach internal networks 7. Close-out —export_loot, thengenerate_report
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 · 70 lines · 1,241 tokens per session scan A 044f69879024
kali-mcp CLAUDE.md is an instructions file published in the GitHub repository puffert/kali-mcp (0 stars, last pushed 29d ago), licensed MIT. It adds 1,241 tokens to every session, about $0.0062 per session on Opus 5. 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-31.
Other instructions, from other repositories
akira AGENTS.md
Instructions for kalpmodi/akira, covering akira - ai agent adapter, what akira does, skill index, how to use and phase artifacts.
red-run CLAUDE.md
Claude Code instructions for blacklanternsecurity/red-run, covering red-run, engagement workflow, token budget, architecture and orchestrator variants.
pentest-mcp-server AGENTS.md
AGENTS.md instructions for cyanheads/pentest-mcp-server, covering developer protocol, core rules, patterns, tool (representative — pentestlookuptechnique) and server instructions.
pentest-mcp-server CLAUDE.md
Claude Code instructions for cyanheads/pentest-mcp-server, covering developer protocol, core rules, patterns, tool (representative — pentestlookuptechnique) and server instructions.
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).