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/lgbarn/shipyard/cancelgit clone --depth 1 https://github.com/lgbarn/shipyardWrote 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/lgbarn/shipyard/cancel)<a href="https://agentmods.dev/commands/lgbarn/shipyard/cancel"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/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.00007 | $0.00485 |
| Opus 5 | $0.00003 | $0.00243 |
| Sonnet 5 | $0.00001 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00049 |
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.
What it actually says
/shipyard:cancel — Graceful Pause
You are executing the Shipyard cancel workflow. This pauses in-progress work and creates a checkpoint for later resumption.
Step 1: Check State Exists
Check if .shipyard/STATE.json exists.
- If it does not exist:
Display:
"No active Shipyard work to cancel. No
.shipyard/STATE.jsonfound." Stop here.
Step 2: Read Current State
Follow State Loading Protocol — read STATE.json to get current status, phase, and position.
- If status is NOT
building,in_progress, orplanning: Display:"No active work in progress. Current status: {status}. Nothing to cancel." Stop here.
Step 3: Create Checkpoint
Create a git checkpoint so work can be resumed:
# Create checkpoint tag with current state
git tag "shipyard-checkpoint-$(date +%Y%m%d-%H%M%S)" -m "Shipyard cancel checkpoint: phase {phase}, status {status}"
Step 4: Update State to Paused
Update STATE.json:
- Set
statusto"paused" - Preserve
phaseandposition
Append to HISTORY.md:
- [{timestamp}] Paused: phase {phase}, position {position} (user-initiated cancel)
Use bash scripts/state-write.sh with appropriate arguments.
Step 5: Report Pending Work
Scan for any in-progress artifacts:
- Check for uncommitted changes (
git status) - Check for unfinished plan tasks (SUMMARY files without completion)
- Check for active worktrees related to current phase
Step 6: Summary
Display:
Shipyard Cancel
═══════════════════════════════════════════
Phase {N} paused at: {position}
Checkpoint: shipyard-checkpoint-{timestamp}
Uncommitted changes: {yes/no}
Pending tasks: {count}
To resume: /shipyard:resume
To rollback: /shipyard:rollback
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 · 86 lines · 7 tokens per session scan A d6ee119d6bce
cancel is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 485 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
sw-init
Project setup. Creates constitution and charter. Configures gates.
sw-doctor
Read-only installation health check with repair hints.
sw-guard
Detect stack and configure deterministic guardrails.
sw-status
Show current Specwright state and progress.
sw-pivot
Research-backed rebaselining for planning, building, or verifying work. Preserves completed and shipped scope while revising remaining design, plan, and in-progress work.
sw-ship
Strategy-aware merge via pull request. If branch-head freshness blocks and policy is rebase or merge, recover in the same run; manual is the fallback and still reruns /sw-verify before /sw-ship.