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/recovergit 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/recover)<a href="https://agentmods.dev/commands/lgbarn/shipyard/recover"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/recover.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.00009 | $0.00894 |
| Opus 5 | $0.00005 | $0.00447 |
| Sonnet 5 | $0.00002 | $0.00179 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
recover 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 6d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:recover - State Recovery
You are executing the Shipyard recovery workflow. Follow these steps precisely.
Step 1: Verify State Exists
Check if .shipyard/ directory exists.
- If it does not exist:
"No Shipyard project detected. Nothing to recover. Run
/shipyard:initto start fresh." Stop here.
Step 2: Diagnose State
Follow State Loading Protocol (read STATE.json, HISTORY.md, ROADMAP.md, PROJECT.md, config.json, and recent SUMMARY/VERIFICATION files to establish session context; see docs/PROTOCOLS.md) -- read STATE.json, HISTORY.md, ROADMAP.md, config.json, and recent artifacts. Then check for inconsistencies:
Check for these inconsistencies:
| Symptom | Diagnosis |
|---|---|
| Status says "building" but no SUMMARY.md files exist for current phase | Build was interrupted before any task completed |
| Status says "building" and some SUMMARY.md exist but not all | Build was interrupted mid-phase |
| Status says "planning" but no PLAN.md files exist | Planning was interrupted before architect completed |
| REVIEW.md shows CRITICAL_ISSUES with no subsequent fix commits | Review issues were never addressed |
| STATE.json is missing or empty | State file was corrupted or deleted |
| STATE.json references a phase that doesn't exist in ROADMAP.md | State and roadmap are out of sync |
| SUMMARY.md shows "partial" or "failed" status | Task execution failed |
Step 3: List Available Checkpoints
Run git tag -l "shipyard-checkpoint-*" --sort=-version:refname and identify the most recent checkpoint.
Step 4: Present Diagnosis
Display a clear diagnosis:
Recovery Diagnosis
══════════════════
State: {description of what STATE.json says}
Actual: {description of what artifacts exist}
Problem: {what is inconsistent}
Last checkpoint: {most recent checkpoint tag, or "none"}
Recommended action: {see options below}
Step 5: Present Recovery Options
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.
- 6d ago First seen · 108 lines · 9 tokens per session scan A b32b82787772
recover is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 894 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-debug
Investigation-first debugging. Scope, investigate, diagnose, then fix/log/defer.
doctor
Health check for greatcto. Shows pipeline state, missing artefacts, hook status, last run per agent, and permission-denied tail.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
debug
Systematic debugging with hypotheses and evidence gathering.
data-flow-analysis
Trace how data flows through the system from input to output.
duck-off
Turn off Rubber Duck mode and answer normally.