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-start.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-start)<a href="https://agentmods.dev/commands/pabpereza/kali-mcp/kali-start"><img src="https://agentmods.dev/badge/commands/pabpereza/kali-mcp/kali-start/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-start"><img src="https://agentmods.dev/badge/commands/pabpereza/kali-mcp/kali-start.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.00565 |
| Opus 5 | $0.00000 | $0.00282 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
kali-start 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 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.
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize a penetration testing session for target: $ARGUMENTS
You are the session manager. Set up the session workspace before any scanning begins.
Step 1: Collect Session Parameters
Parse the target(s) from $ARGUMENTS if present (comma-separated for multiple). Then use a single AskUserQuestion call with up to two questions (skip any already answered by $ARGUMENTS):
- Target(s) (only if not in
$ARGUMENTS): "Enter the target(s) for this engagement (IP, hostname, URL, or CIDR range):" - Authorization scope: "Select the authorization scope for this engagement:"
- Passive only — scanning and vulnerability identification, no brute force, no exploitation.
- Passive + Credential testing — adds brute force with small wordlists.
- Full pentest — all phases including exploitation. May cause service disruption.
There is a single engagement type — /kali-audit — so no need to ask about it.
Step 2: Create the Session
- Sanitize the target name (replace
/,:,.with_), timestamp withdate +%Y%m%d_%H%M. mkdir -p sessions/<sanitized_target>_<timestamp>/assets- Write
sessions/<dir>/session.md:# Pentest Session - **Target(s)**: <target list> - **Date**: <current date/time> - **Scope**: <authorization scope> - **Status**: IN PROGRESS ## Timeline - [<time>] Session initialized ## Sub-Agents Dispatched _None yet._ ## Summary _In progress. Run `/kali-finish` when done._ - Write
sessions/<dir>/targets.md:# Targets | Target | Status | Findings | |--------|--------|----------| | <target> | Pending | — | ## Scope **Authorization level**: <scope> - Write an empty
sessions/<dir>/assets/.gitkeepso the directory is tracked.
Step 3: Present Summary
SESSION INITIALIZED
━━━━━━━━━━━━━━━━━━
Target(s): <targets>
Scope: <authorization scope>
Directory: sessions/<dir>/
Next: /kali-audit <target>
Then: /kali-finish — finalize, report, and consolidate tool-efficiency lessons
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 · 66 lines · 0 tokens per session scan A ee58e2a8fe66
kali-start 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 565 tokens. 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-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.