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/shipgit 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.00005 | $0.03213 |
| Opus 5 | $0.00003 | $0.01606 |
| Sonnet 5 | $0.00001 | $0.00643 |
| Haiku 4.5 | $0.00001 | $0.00321 |
Grade A, and why
ship 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:ship - Delivery & Completion
You are executing the Shipyard shipping workflow. Follow these steps precisely.
Step 1: Parse Arguments & Load Context
Determine the shipping scope:
--phase-- Ship only the current phase (partial delivery)--milestone-- Ship the entire milestone (default if all phases complete)--branch-- Ship whatever is on the current branch- No argument -- auto-detect the appropriate scope
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_routing from config; see docs/PROTOCOLS.md) -- read model_routing from config for agent model selection.
Step 1a: 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)
Question text: "Teams available. Use team mode (parallel teammates) or agent mode (subagents)?"
Silent fallback: If SHIPYARD_TEAMS_ENABLED is false or unset, silently set dispatch_mode to agent with no prompt (zero overhead).
Variable storage: Store the result as dispatch_mode (value: team or agent). This variable is referenced by all subsequent dispatch steps.
Recommendation: For the ship command, agent mode is preferred. The sequential workflow (verify → audit → document → deliver) has no parallelism benefit from team mode. All dispatch steps below use Task dispatch regardless of dispatch_mode. The dispatch section is included for consistency with other Shipyard commands.
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 · 333 lines · 5 tokens per session scan A 0b292e62d97e
ship is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 3,213 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.