Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitnpx agentmods add commands/random6913/claude-code-superkit/stopWrote 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/random6913/claude-code-superkit/stop)<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/stop"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/stop/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/random6913/claude-code-superkit/stop"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/stop.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.00012 | $0.00240 |
| Opus 5.5 | $0.00005 | $0.00096 |
| Sonnet 5.5 | $0.00002 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
stop 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 1mo 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.
What it actually says
Stop Full Local Stack (Claude Code)
Stop all services started by Claude Code. Docker containers keep running by default.
Steps
Run the Claude Code stop script:
bash .claude/scripts/stop.sh
For stopping Docker too (PostgreSQL, Redis, MinIO):
bash .claude/scripts/stop.sh --with-docker
Report the result to the user.
What Gets Stopped
- LaunchAgents — unloads all
com.myapp.*plist files to prevent auto-restart - Tracked PIDs — kills processes from
~/.config/myapp/claude-code/pids - Orphan processes — kills
go run,vite,npm dev,cloudflaredby pattern match - Docker (with
--with-docker) —docker compose downfor PostgreSQL, Redis, MinIO - Verification — checks no processes remain, warns if any survive
$ARGUMENTS
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.
- 1mo ago First seen · 35 lines · 12 tokens per session scan A 78c89cd10c79
stop is a command published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 240 once invoked, about $0.0000 per session on Opus 5.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-09-03.
Other commands, from other repositories
ops-k8s
Kubernetes deployment and orchestration.
send
Send a message to another Conductor workspace.
setup-mcp-claude-code
Build and register the Contorium MCP server for Claude Code or Cursor Agent.
orgkit-cadence
Analyze your real Claude Code usage and recommend a capture cadence + time slot, then optionally install a low-impact background batch-capture cron. Read-only analysis; the cron is opt-in.
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.