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-finish.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-finish)<a href="https://agentmods.dev/commands/pabpereza/kali-mcp/kali-finish"><img src="https://agentmods.dev/badge/commands/pabpereza/kali-mcp/kali-finish/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-finish"><img src="https://agentmods.dev/badge/commands/pabpereza/kali-mcp/kali-finish.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.00893 |
| Opus 5 | $0.00000 | $0.00447 |
| Sonnet 5 | $0.00000 | $0.00179 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
kali-finish 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 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.
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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finalize the current penetration testing session and generate the consolidated report.
You are the session finalizer: review sub-agent outputs, double-check completeness, produce the final report, and fold any reusable tool-efficiency lessons back into knowledge/.
Step 1: Locate the Session
ls -td sessions/*/ 2>/dev/null | head -1
If none exists: tell the user "No active session found. Use /kali-start <target> to initialize one first." and stop.
Read sessions/<dir>/session.md and targets.md for context.
Step 2: Inventory & Double-Check
Glob sessions/<dir>/assets/**/*, read every asset file, and build a quality table:
| Sub-Agent | Asset File | Status | Quality | Notes |
|---|---|---|---|---|
| ... | Complete/Partial/Missing | Good/Fair/Poor | ... |
Check each for: actual scan output (not just errors), the expected tools were really run, findings carry severity, evidence is present.
Step 3: Gaps
List missing/failed sub-agents, untested discovered services, and approved-but-unexecuted scope items. If any exist, AskUserQuestion: "Gaps detected. How should we proceed?"
- Re-run missing scans — dispatch sub-agents for the gaps, wait, then continue.
- Proceed with partial results — finalize now, noting gaps.
- Cancel — don't finalize yet.
Step 4: Compile Findings
Read all asset files, deduplicate, and write sessions/<dir>/findings.md:
# Consolidated Findings
**Session**: <target> | <date> | <scope>
**Total findings**: <count>
## Critical / High / Medium / Low / Informational
| # | Finding | Service | Port | Evidence | Remediation |
## Attack Paths
## Gaps & Limitations
Step 5: Update Session File
Edit session.md: status → COMPLETED, executive summary (3-5 sentences), full sub-agent list, final timeline entry, and:
## Statistics
- Critical/High/Medium/Low: <n> each, Total: <n>
- Assets generated: <n>, Sub-agents run: <n>, Gaps detected: <n>
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 · 81 lines · 0 tokens per session scan A ced02b6a85f5
kali-finish 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 893 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.