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/statusgit 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.00764 |
| Opus 5 | $0.00004 | $0.00382 |
| Sonnet 5 | $0.00002 | $0.00153 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
status 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:status - Progress Dashboard
You are executing the Shipyard status workflow. Follow these steps precisely.
Step 1: Check State Exists
Check if .shipyard/ directory exists.
- If it does not exist:
Display:
"No Shipyard project detected in this directory. Run
/shipyard:initto get started." Stop here.
Step 2: Read State Files
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).
Step 3: Display Native Task Progress
Follow Native Task Scaffolding Protocol (create/update native tasks for progress tracking via TaskCreate/TaskUpdate; see docs/PROTOCOLS.md) -- call TaskList to show the current state of all Shipyard-created native tasks.
Step 4: Display Dashboard
Present a comprehensive status display:
Progress Visualization
Show phase progress in a clear format:
Roadmap: {milestone_name}
═══════════════════════════════════════════
Phase 1: {title} [COMPLETE]
Phase 2: {title} [IN PROGRESS - Building]
- Plan 2.1: {title} [COMPLETE]
- Plan 2.2: {title} [IN PROGRESS]
- Plan 2.3: {title} [NOT STARTED]
Phase 3: {title} [NOT STARTED]
Overall: {X}/{Y} phases complete
Current Position
From STATE.json:
- What phase and step we're on
- What was last completed
- When it was last updated
Recent Activity
From the most recent SUMMARY.md files:
- Last 3-5 completed actions
- Files recently modified
- Key decisions made
Blockers & Issues
From STATE.json, HISTORY.md, and REVIEW.md files:
- Any unresolved critical issues
- Any blocked tasks
- Any gaps identified
Step 5: Intelligent Routing
Based on the current state, suggest the most appropriate next action:
| State | Suggestion |
|---|---|
No .shipyard/ directory |
/shipyard:init -- Initialize the project |
| Phase exists but has no plans | /shipyard:plan {N} -- Plan the current phase |
| Plans exist but none executed | /shipyard:build {N} -- Begin building |
| Build in progress, interrupted | /shipyard:resume -- Restore context and continue |
| Phase complete with gaps | /shipyard:plan {N} --gaps -- Fill the gaps |
| Phase fully complete, more remain | /shipyard:plan {N+1} -- Plan the next phase |
| All phases complete | /shipyard:ship -- Finalize and deliver |
| Milestone shipped (status: shipped) | /shipyard:brainstorm -- Define goals for the next milestone |
| Critical issues found | Review issues, then /shipyard:build {N} --plan W.P to retry specific plans |
| Quick task needed | /shipyard:quick {description} -- Execute outside the roadmap |
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 · 103 lines · 8 tokens per session scan A 2653e70749e3
status 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 764 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.