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.
git 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/build)<a href="https://agentmods.dev/commands/lgbarn/shipyard/build"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/build/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/lgbarn/shipyard/build"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/build.svg" alt="Reviewed on agentmods" width="80" 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.04393 |
| Opus 5.5 | $0.00004 | $0.01757 |
| Sonnet 5.5 | $0.00002 | $0.00879 |
| Haiku 4.5 | $0.00001 | $0.00439 |
Grade A, and why
build 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 1mo 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:build - Plan Execution
You are executing the Shipyard build workflow. Follow these steps precisely.
Step 1: Parse Arguments
- If a phase number is provided, use it.
- If
--plan Nis provided, execute only that specific plan (format: W.P). - If
--lightis provided, skip post-phase auditor and simplifier (Steps 5a and 5b). Use this during early iteration — the full pipeline runs at ship time regardless. - If no phase number, read
.shipyard/STATE.jsonfor the current phase. - Read
.shipyard/config.jsonfor gate preferences (security_audit,simplification_review,iac_validation,documentation_generation). - Follow Worktree Protocol (detect if running in a git worktree; if so, use worktree root for paths and record the branch name; see
docs/PROTOCOLS.md) -- detect worktree, record working directory and branch. - Follow Model Routing Protocol (select the correct model for each agent role using
model_routingfrom config; seedocs/PROTOCOLS.md) -- readmodel_routingfrom config for agent model selection.
Step 2: Validate State
- Verify
.shipyard/exists. If not, tell the user to run/shipyard:initfirst. - Read
.shipyard/ROADMAP.mdand locate the target phase. - Read
.shipyard/STATE.jsonfor current context. - Load all plan files from
.shipyard/phases/{N}/plans/. - Check which plans have already been completed (have SUMMARY.md files in
.shipyard/phases/{N}/results/). - If all plans are complete, inform the user and suggest
/shipyard:shipor next phase.
Step 2b: Team or Agent Dispatch
Detection: Check the SHIPYARD_TEAMS_ENABLED environment variable (exported by scripts/team-detect.sh). This variable is set to true when CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
Prompt (conditional): If SHIPYARD_TEAMS_ENABLED=true, use AskUserQuestion with exactly two options:
- "Team mode (parallel teammates)" -- uses TeamCreate/TaskCreate/SendMessage/TeamDelete lifecycle
- "Agent mode (subagents)" -- uses standard Task dispatch (current behavior)
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.
- 1mo ago First seen · 378 lines · 9 tokens per session scan A 22aada1ed0d3
build is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 4d ago), licensed MIT. It adds 9 tokens to every session and 4,393 once invoked, about $0.0000 per session on Opus 5.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-audit
Periodic codebase health check for systemic technical debt.
sw-review
PR comment review. Group by status and respond inline.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
init
Install the formatters this repository needs, with every command visible before it runs.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
extend
Capture a mid-PR sub-idea and implement it onto the current open PR's branch — no new branch, no new PR. Preserves Verify → Review → Deliver.