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-feature-retrygit clone --depth 1 https://github.com/jsegov/shipspec-claude-code-pluginWrote 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/commands/jsegov/shipspec-claude-code-plugin/cancel-feature-retry)<a href="https://agentmods.dev/commands/jsegov/shipspec-claude-code-plugin/cancel-feature-retry"><img src="https://agentmods.dev/badge/commands/jsegov/shipspec-claude-code-plugin/cancel-feature-retry.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.1 | $0.00006 | $0.00542 |
| Opus 5 | $0.00003 | $0.00271 |
| Sonnet 5 | $0.00001 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
cancel-feature-retry 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 5d 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 Feature Retry
Cancel an active feature implementation retry 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 feature retry loop found."
Stop here.
If POINTER_EXISTS: Read the pointer file and verify it's a feature-retry:
jq -r '.loop_type // empty' .shipspec/active-loop.local.json
If loop_type is NOT "feature-retry":
"No active feature retry 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 '.current_task_id // empty' [state_path]
jq -r '.feature // empty' [state_path]
jq -r '.task_attempt // 0' [state_path]
jq -r '.max_task_attempts // 5' [state_path]
jq -r '.tasks_completed // 0' [state_path]
jq -r '.total_tasks // 0' [state_path]
current_task_id- the task being implementedfeature- the feature nametask_attempt- current attempt number for the taskmax_task_attempts- maximum attempts per tasktasks_completed- number of completed taskstotal_tasks- total number of tasks
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 feature retry for [FEATURE]
- Current task: [CURRENT_TASK_ID] (attempt [TASK_ATTEMPT]/[MAX_TASK_ATTEMPTS])
- Progress: [TASKS_COMPLETED]/[TOTAL_TASKS] tasks completed
The current task remains in
in_progressstatus in TASKS.json. Run/implement-feature [feature]to resume, or/implement-task [feature]to continue task-by-task."
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.
- 5d ago First seen · 78 lines · 6 tokens per session scan A dd957b36c79e
cancel-feature-retry is a command published in the GitHub repository jsegov/shipspec-claude-code-plugin (20 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 542 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
spec-kitty.implement
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
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.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
kiro-validate-design
Command "kiro-validate-design" from gotalab/cc-sdd, covering technical design validation, core task, execution steps, important constraints and tool guidance.