kali-mcp: Command for Claude Code

.claude/commands/kali-audit.md

kali-audit is a command for Claude Code from pabpereza/kali-mcp. It costs 0 tokens per session (2,552 once invoked), scanned A, original, MIT.

A command for coordinating a full security audit or penetration test of a specified target, including service discovery and specialized testing agents.

In plain words
What is it for?
Use it to inspect exposed services, launch security checks in waves, and compile a final audit report for a target you are authorized to test.
Why use it?
It organizes the audit into saved sessions and stages so findings, files, and progress stay together. It also asks for authorization before testing begins.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions subagents; names the AskUserQuestion tool.

This is pabpereza/kali-mcp's own configuration. It tells Claude Code how to work on kali-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kali-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/pabpereza/kali-mcp/main/.claude/commands/kali-audit.md
Clone the repo
git clone --depth 1 https://github.com/pabpereza/kali-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for kali-audit

README.md
[![agentmods](https://agentmods.dev/badge/commands/pabpereza/kali-mcp/kali-audit/github.svg)](https://agentmods.dev/commands/pabpereza/kali-mcp/kali-audit)
Your own site
<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.

agentmods 80×15 button for kali-audit

Your own site · 80×15
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,552 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 11d ago against content hash 3f891995c310, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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
.claude/commands/kali-audit.md · 114 lines

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

  1. Check for an existing session: ls -td sessions/*/ 2>/dev/null | head -1. If it exists and session.md shows IN PROGRESS, reuse it.
  2. Otherwise create one: sanitize the target (replace /, :, . with _), timestamp with date +%Y%m%d_%H%M, mkdir -p sessions/<sanitized_target>_<timestamp>/assets, write session.md (target, date, type: Audit, status: IN PROGRESS) and targets.md.
  3. Store the path as SESSION_DIR. Every sub-agent below MUST receive SESSION_DIR in its prompt.

Phase 1: Discovery (you do this yourself)

  1. Fast pass (blocking): execute_command with nmap -sV -sC -O -Pn --top-ports 1000 -T4 <target> (-O works — the container has NET_RAW/NET_ADMIN). Start Wave A from this.
  2. 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.
  3. 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:"

  1. Passive only — Recon and vulnerability identification. No brute force, no exploitation, no sqlmap.
  2. Passive + Credential testing — Adds brute force with small wordlists against discovered login services.
  3. Full pentest — Adds SQL injection exploitation, command injection, sensitive file exfiltration, AD/SMB exploitation, and exploit verification. May cause service disruption.
  4. Cancel — Do not proceed.

Read the full file on GitHub · 114 lines

Changes

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.

  1. 11d ago First seen · 114 lines · 0 tokens per session scan A 3f891995c310

Subscribe to this mod's changes

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.