Borrowing it
Nothing to install: this file belongs to pabpereza/kali-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pabpereza/kali-mcp/main/.claude/commands/kali-audit.mdgit clone --depth 1 https://github.com/pabpereza/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/commands/pabpereza/kali-mcp/kali-audit)<a href="https://agentmods.dev/commands/pabpereza/kali-mcp/kali-audit"><img src="https://agentmods.dev/badge/commands/pabpereza/kali-mcp/kali-audit/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/pabpereza/kali-mcp/kali-audit"><img src="https://agentmods.dev/badge/commands/pabpereza/kali-mcp/kali-audit.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.00000 | $0.02552 |
| Opus 5 | $0.00000 | $0.01276 |
| Sonnet 5 | $0.00000 | $0.00510 |
| Haiku 4.5 | $0.00000 | $0.00255 |
Grade A, and why
kali-audit 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 11d 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.
**Web Directory & Sensitive Content Enumeration** — ffuf directory + file fuzzing (`raft-medium-directories.txt`, `raft-medium-files.txt`), curl sweep of common sensitive endpoints (`.env`, `.git/`, `/api-docs`, `/actuat How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perform a full security audit / penetration test on the target: $ARGUMENTS
You are the ORCHESTRATOR. Your ONLY job: discover services, ask authorization, launch specialized sub-agents in parallel across two waves (loot before exploitation), and compile the final report. Do NOT run scans yourself beyond the initial nmap discovery.
Phase 0: Session Management
- Check for an existing session:
ls -td sessions/*/ 2>/dev/null | head -1. If it exists andsession.mdshowsIN PROGRESS, reuse it. - Otherwise create one: sanitize the target (replace
/,:,.with_), timestamp withdate +%Y%m%d_%H%M,mkdir -p sessions/<sanitized_target>_<timestamp>/assets, writesession.md(target, date, type: Audit, status: IN PROGRESS) andtargets.md. - Store the path as
SESSION_DIR. Every sub-agent below MUST receiveSESSION_DIRin its prompt.
Phase 1: Discovery (you do this yourself)
- Fast pass (blocking):
execute_commandwithnmap -sV -sC -O -Pn --top-ports 1000 -T4 <target>(-Oworks — the container has NET_RAW/NET_ADMIN). Start Wave A from this. - Full pass (background): also kick off
nmap -p- -T4 -Pn <target>in the background to catch high/uncommon ports; fold any extras into the target list, dispatching late sub-agents if needed. - Parse results into a table of open ports, service names, and versions. Print it.
Phase 1.5: Knowledge Lookup
Read knowledge/tools/index.md if it exists. For each tool you're about to dispatch sub-agents to run (gobuster, hydra, nikto, nuclei, etc. — whatever the discovered services call for), read the matching knowledge/tools/<tool>.md and fold its "What works well" notes into that sub-agent's prompt as one line: KNOWN EFFICIENCY NOTES: <notes>. Skip silently for tools with no file yet — this is a lookup, not a requirement.
Phase 2: Authorization
Use AskUserQuestion: "Select the authorization scope for this engagement:"
- Passive only — Recon and vulnerability identification. No brute force, no exploitation, no sqlmap.
- Passive + Credential testing — Adds brute force with small wordlists against discovered login services.
- Full pentest — Adds SQL injection exploitation, command injection, sensitive file exfiltration, AD/SMB exploitation, and exploit verification. May cause service disruption.
- Cancel — Do not proceed.
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.
- 11d ago First seen · 114 lines · 0 tokens per session scan A 3f891995c310
kali-audit is a command published in the GitHub repository pabpereza/kali-mcp (57 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,552 tokens. 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.