Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/hunterg325/claude-code-pm/pm-stopnpx skills add hunterg325/claude-code-pm --skill pm-stopgit clone --depth 1 https://github.com/hunterg325/claude-code-pmWrote 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/skills/hunterg325/claude-code-pm/pm-stop)<a href="https://agentmods.dev/skills/hunterg325/claude-code-pm/pm-stop"><img src="https://agentmods.dev/badge/skills/hunterg325/claude-code-pm/pm-stop.svg" alt="Measured on agentmods" 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 | $0.00041 | $0.00326 |
| Opus 5 | $0.00020 | $0.00163 |
| Sonnet 5 | $0.00008 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
pm-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 4d 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
/pm:stop — Graceful Shutdown
Shutdown Sequence
- Read
.claude/pm-state.jsonfor active state - For each active worker:
- Send
abortmessage via claude-peers:{ "type": "abort", "task_id": "{id}", "reason": "PM shutting down" } - Log the abort
- Send
- For each active VO agent:
- Send abort message
- Wait up to 30 seconds for workers to acknowledge (responses arrive as events)
- Update pm-state.json:
- Move active workers to a
shutdown_pendingstate - Record shutdown timestamp
- Move active workers to a
- Report summary:
- Workers notified: N
- Workers acknowledged: N
- Tasks that were in progress (may need re-queue on next /pm:start)
Optional Cleanup
Ask user: "Would you like to clean up orphaned worktrees? This removes worktrees for tasks that haven't been merged."
If yes:
- Run
git worktree list - Cross-reference with merged branches
- Remove unmerged worktrees with confirmation for each
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.
- 4d ago First seen · 38 lines · 41 tokens per session scan A 496a16c4dced
pm-stop is a skill published in the GitHub repository hunterg325/claude-code-pm (2 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 326 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
run
Conduct a task end to end, from a one-line fix to a multi-day programme - a short interview, then autonomous execution to the finish. Classifies the task S/M/L/XL, configures itself to the repo, routes each role to a cost tier, drives the agent team from the kanban board, and stops only at genuine decisions. Use for…
status
Where is the work right now. Regenerates the projections and the kanban board from the journal and answers with the progress line, the agents still running, the open gates and the resume steps. Read-only. Use for /tyran:status or when asked what is going on.
heartbeat
This skill should be used when the user asks to "run a heartbeat", "run the agent loop", "process GitHub issues", "check for work", or runs the /heartbeat command. Executes the WoterClip heartbeat — picks up GitHub issues, resolves personas, does work, and reports back.
woterclip-init
This skill should be used when the user asks to "initialize woterclip", "set up woterclip", "woterclip init", "configure woterclip for this repo", or runs the /woterclip-init command. Scaffolds a repo with WoterClip config, persona directories, and GitHub labels.
unleash
Run as a named worker draining the task queue in my private coordination repo, where each task is a GitHub Issue — claim one task at a time, check blocked-by dependencies, plan with explicit assumptions, execute, validate against acceptance criteria, and record results as comments; then stay in ambush behind a…
status
Read-only console of a kraken queue — everything the operator reads in one place. Runs kraken.py status, which computes the review queue (awaiting-merge, with PR links), the decision queue (needs-decision), what is still in flight (every live claim ref — worker name + lease age, flagging expired leases), a…