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 commands/gantisstorm/essentials-claude-code/cancel-teamgit clone --depth 1 https://github.com/GantisStorm/essentials-claude-codeWhat 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.00005 | $0.00299 |
| Opus 5 | $0.00003 | $0.00150 |
| Sonnet 5 | $0.00001 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
cancel-team 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 2d 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
Cancel Team
Stop any active agent team and terminate tmux panes.
Works with all team commands: /implement-team, /plan-team.
Note: Use /cancel-team for teams, /cancel-swarm for swarms, and /cancel-loop for loops.
Instructions
- Call TaskList to see all tasks and their status
- For any tasks with status
in_progress:- Note the task subjects (agent assignments)
- Agents may still be running in tmux panes
- Terminate agent tmux panes by running:
tmux kill-session -t claude-team 2>/dev/null || true - Report:
- Completed tasks: N
- In-progress (interrupted): N
- Pending (not started): N
If no in-progress tasks found:
- Say "No active team found."
After Cancellation
Task progress is preserved:
- Completed tasks remain completed
- In-progress agent work may be partially saved (agents are full Claude Code instances)
- Pending tasks remain pending
To check task status:
TaskList
Note
Unlike swarm cancellation (which stops lightweight subagents), team cancellation terminates full Claude Code instances running in tmux panes. Work completed by agents before cancellation is saved to disk.
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.
- 2d ago First seen · 46 lines · 5 tokens per session scan A 77d15ee62b87
cancel-team is a command published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 5 tokens to every session and 299 once invoked, about $0.0000 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-30.
Other commands, from other repositories
analyze-repo
Analyze an existing repository's structure, conventions, and guardrails.
go-test
Go TDD workflow with table-driven tests.
retex
Retex - Capture lesson learned dans memory après fix, rollback, erreur.
go-review
Go code review for idiomatic patterns.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
doctor
Run IJFW health check (files, MCP server, hooks, memory, caps, framing).