← ClaudeAtlas

agent-kill-switchlisted

Give the human an off switch and a cost meter for the coding agents on this machine, using ClawMetry. Use when the user asks to stop or kill a runaway agent, see what an agent is doing or spending, cap agent spend, gate risky tool calls behind approval, or "set up a kill switch" for Claude Code, Codex, Cursor, Gemini CLI, OpenClaw, Goose, Aider and similar runtimes.
vivekchand/clawmetry · ★ 436 · AI & Automation · score 90
Install: claude install-skill vivekchand/clawmetry
# Agent kill switch An agent that loops, re-reads the same files, or shells out to something it should not is expensive by the minute. This skill wires up [ClawMetry](https://github.com/vivekchand/clawmetry), a local, read-only dashboard that reads the session logs the runtimes already write on disk, and uses it for three things: see what is running, stop one session, and hold risky tool calls until a human says yes. Nothing here modifies the agent. Observation is read-only. Every control below is opt-in and stated as what it does, so tell the user exactly which ones you enabled. ## 1. Install and start ```bash pip install clawmetry && clawmetry ``` The dashboard is at `http://localhost:8900`. It auto-detects the runtimes on the machine (Claude Code, Codex, Cursor, Gemini CLI, OpenClaw, Goose, Aider, Cline, OpenCode and others); no config. Confirm it is up: ```bash curl -s http://localhost:8900/api/overview | head -c 400 ``` If the port is taken: `clawmetry --port 8901` and use that port below. ## 2. See what is running and what it costs ```bash curl -s http://localhost:8900/api/sessions # live and recent sessions, ids look like claude_code:<uuid> curl -s http://localhost:8900/api/usage # tokens and cache-aware cost per model and per session ``` Tell the user in plain words: which sessions are active, which one is spending the most, and whether any is showing loop signs. The dashboard's Sessions tab shows the full transcript and every tool call for a se