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/jsegov/shipspec-claude-code-plugin/cancel-task-loopgit clone --depth 1 https://github.com/jsegov/shipspec-claude-code-pluginWhat 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.00449 |
| Opus 5 | $0.00003 | $0.00225 |
| Sonnet 5 | $0.00001 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
cancel-task-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 Task Loop
Cancel an active task implementation loop.
Step 1: Check for Active Loop
Check for the pointer file:
test -f .shipspec/active-loop.local.json && echo "POINTER_EXISTS" || echo "NOT_FOUND"
If NOT_FOUND:
"No active task loop found."
Stop here.
If POINTER_EXISTS: Read the pointer file and verify it's a task-loop:
jq -r '.loop_type // empty' .shipspec/active-loop.local.json
If loop_type is NOT "task-loop":
"No active task loop found. (A different loop type is active)"
Stop here.
Step 2: Read Current State
Extract the state path from the pointer:
jq -r '.state_path // empty' .shipspec/active-loop.local.json
Parse the state file (JSON) to extract:
jq -r '.task_id // empty' [state_path]
jq -r '.feature // empty' [state_path]
jq -r '.iteration // 0' [state_path]
jq -r '.max_iterations // 5' [state_path]
task_id- the task being implementedfeature- the feature nameiteration- current attempt numbermax_iterations- maximum attempts configured
Step 3: Cancel the Loop
Remove both the state file and pointer:
rm -f [state_path] .shipspec/active-loop.local.json
Step 4: Report
"Cancelled task loop for [TASK_ID] in feature [FEATURE]
- Was at iteration: [ITERATION]/[MAX_ITERATIONS]
The task remains in
in_progressstatus in TASKS.json. Run/implement-task [feature]to resume, or use task-manager to update the task status."
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 · 73 lines · 5 tokens per session scan A 0cdc6d7ec27a
cancel-task-loop is a command published in the GitHub repository jsegov/shipspec-claude-code-plugin (20 stars, last pushed 7mo ago), licensed MIT. It adds 5 tokens to every session and 449 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
kiro-steering-custom
Command "kiro-steering-custom" from gotalab/cc-sdd, covering kiro custom steering creation, workflow, available templates, steering principles and tool guidance.
bench-capture
Score the 2 bench variant folders for one size (build/acceptance/regression/conventions/capture + rubric + cross-solution review), record, report, and reset.
autospec.plan
Generate YAML implementation plan from feature specification.
kiro-validate-design
Command "kiro-validate-design" from gotalab/cc-sdd, covering technical design validation, core task, execution steps, important constraints and tool guidance.
deploy
Build, test, deploy with staged rollout.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.