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/shousper/claude-kit/cancelnpx skills add shousper/claude-kit --skill cancelgit clone --depth 1 https://github.com/shousper/claude-kitWrote 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/shousper/claude-kit/cancel)<a href="https://agentmods.dev/skills/shousper/claude-kit/cancel"><img src="https://agentmods.dev/badge/skills/shousper/claude-kit/cancel.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.00087 | $0.00662 |
| Opus 5 | $0.00044 | $0.00331 |
| Sonnet 5 | $0.00017 | $0.00132 |
| Haiku 4.5 | $0.00009 | $0.00066 |
Grade A, and why
cancel 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cancel Story Run
The escape hatch. Stopping is cheap, safe, and never loses work — say so, then do it.
Process
1. Stop the loop
Loops are per-session — stopping one worker's loop needs its session id (or run this from that worker's own session, which supplies it automatically via CLAUDE_SESSION_ID); stopping every loop on the board needs --all.
story loop status --json # no session: lists every active loop on the board
story loop status --session <id> --json # one worker's loop — capture goal + iterations used vs budget BEFORE stopping
story loop stop --session <id> # stop that one worker's loop — returns {stopped: true|false}
story loop stop --all # stop every loop on the board
Report the goal and iterations-vs-budget from the status output. If status reports no active loop ({active: false}), say so and continue to the report — the human still wants the picture.
2. Settle the in-flight story
If this session has a claimed in-progress story, ask your human partner which of:
- Finish it — one last pass through gates and
story done. - Park it —
story park <id> --question "Cancelled mid-work: <current state, what remains>". - Release it —
story update <id> --status todo(work stays on the story branch; the worktree remains for the next claimant).
Never decide silently, and never leave it dangling without asking — a dead lease is reclaimable, but the next worker wastes time re-discovering state.
3. Report the board
From story board (and story list --json where detail helps):
- Counts: done / in-progress / in-review / blocked / todo.
- Parked questions, verbatim, with story ids — these are the human's inbox.
- In-review stories awaiting human review or PR merge.
- Other sessions' active claims — do NOT touch them; their leases expire on their own.
What cancel is not
- Not rollback: completed stories stay done; merged code stays merged.
- Not teardown: worktrees, branches, config, and learnings remain — a future stories:work run resumes cleanly.
- Not cleanup of other workers: parallel sessions keep running; stopping them means cancelling in THEIR sessions.
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 · 57 lines · 87 tokens per session scan A 68cd9a583ba7
cancel is a skill published in the GitHub repository shousper/claude-kit (4 stars, last pushed 8d ago), licensed MIT. It adds 87 tokens to every session and 662 once invoked, about $0.0004 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
simulator-reactions
Simulator.Company reactions specialist — comments, events, approvals, ratings and other feedback attached under an actor. Use when the user wants to comment on an actor, reply in a thread, read/like/pin the discussion, mark comments read, or get reaction stats. Activate when the user says "comment on this actor"…
glab-issue
Create, view, update, and manage GitLab issues. Use when working with issue tracking, bug reports, feature requests, or task management. Operations include creating issues, listing with filters, viewing details, adding comments/notes, updating labels/assignees/milestones, closing/reopening, and board management.…