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-loopgit 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.00004 | $0.00245 |
| Opus 5 | $0.00002 | $0.00122 |
| Sonnet 5 | $0.00001 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
cancel-loop 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 Loop
Gracefully stop any active loop while preserving progress.
Works with all loop commands: /implement-loop, /plan-loop, /tasks-loop, /beads-loop.
Note: Use /cancel-loop for loops, /cancel-swarm for swarms, and /cancel-team for Agent Teams.
Instructions
Check for any active loop state file and cancel it:
- Check for
.claude/implement-loop.local.md - Check for
.claude/plan-loop.local.md - Check for
.claude/tasks-loop.local.md - Check for
.claude/beads-loop.local.md
For each found:
- Read iteration info from the file
- Remove the file
- Report: "Cancelled [type] loop at iteration N"
If none found:
- Say "No active loop found."
After Cancellation
Task progress is preserved:
- Completed tasks remain completed
- In-progress/pending tasks remain in their current state
To check task status:
TaskList
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 · 44 lines · 4 tokens per session scan A 101fd67c155f
cancel-loop is a command published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 4 tokens to every session and 245 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
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
version
Display current guide and Claude Code versions.
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.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
execute
Executa o plano aprovado em .first-plan/07-state/plans/. Segue o plano à risca, para se algo invalidar premissa, gera relatório ao final.