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/rollbackgit clone --depth 1 https://github.com/lgbarn/shipyardWhat 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.00008 | $0.00753 |
| Opus 5 | $0.00004 | $0.00377 |
| Sonnet 5 | $0.00002 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
rollback 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:rollback - Checkpoint Rollback
You are executing the Shipyard rollback workflow. Follow these steps precisely.
Step 1: Verify State
- Verify
.shipyard/exists. If not, tell the user there is nothing to roll back. - Verify this is a git repository with at least one commit.
Step 2: List Checkpoints
Run git tag -l "shipyard-checkpoint-*" --sort=-version:refname to find all checkpoints.
- If
--listwas passed, display checkpoints with dates and labels, then stop. - If no checkpoints exist, inform the user:
"No Shipyard checkpoints found. Checkpoints are created automatically during
/shipyard:planand/shipyard:build."
Step 3: Select Checkpoint
- If a specific checkpoint tag was provided, use it. Verify it exists with
git tag -l. - If no argument, show the 5 most recent checkpoints and ask the user to select one:
Available Checkpoints
═════════════════════
1. shipyard-checkpoint-post-build-phase-2-20260131T...
2. shipyard-checkpoint-pre-build-phase-2-20260131T...
3. shipyard-checkpoint-post-plan-phase-2-20260130T...
4. shipyard-checkpoint-post-build-phase-1-20260130T...
5. shipyard-checkpoint-pre-build-phase-1-20260130T...
Select a checkpoint (1-5):
Step 4: Choose Rollback Scope
Ask the user:
"What scope should the rollback cover?"
- State only — Revert
.shipyard/files only (plans, state, roadmap). Code stays as-is.- Full rollback — Revert both
.shipyard/state AND code changes back to the checkpoint.
Step 5: Create Safety Checkpoint
Before any rollback, create a safety checkpoint:
Follow Checkpoint Protocol (create a named git tag for rollback safety at key pipeline stages; see docs/PROTOCOLS.md) -- create pre-rollback checkpoint.
This ensures the current state can be recovered if the rollback was a mistake.
Step 6: Execute Rollback
State-only rollback:
git checkout <checkpoint-tag> -- .shipyard/
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 · 109 lines · 8 tokens per session scan A 117a546d7669
rollback is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 753 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
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.
new
Creates a new item in a module that supports the new capability.
card
Open one self-contained OverClick card.
deep-audit.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Ornek cikti.
design
CPS(Context-Problem-Solution) 프레임워크로 Design 문서를 작성한다.
kimi:crank-next
Dispatch the single highest-priority ready task whose dependencies are satisfied.