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/reviewgit 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/review)<a href="https://agentmods.dev/commands/lgbarn/shipyard/review"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/review.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 | $0.00016 | $0.00695 |
| Opus 5 | $0.00008 | $0.00347 |
| Sonnet 5 | $0.00003 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
review 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 4d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:review - On-Demand Code Review
You are executing an on-demand code review. Follow these steps precisely.
Step 1: Parse Arguments
Extract from the command:
target(optional): What to review. Accepts:- No argument / "current": Review uncommitted changes (
git diff+git diff --cached) - Diff range (e.g.,
main..HEAD,abc123..def456): Review commits in range - File/directory path: Review current state of specific files
- Branch name: Review branch changes vs main (
main..<branch>)
- No argument / "current": Review uncommitted changes (
If no target and no uncommitted changes exist, ask the user what they want reviewed.
Step 2: Detect Context
- Check if
.shipyard/exists (optional — this command works anywhere). - If
.shipyard/config.jsonexists, readmodel_routing.reviewfor model selection. - Otherwise, use default model: sonnet.
- Follow Worktree Protocol (see
docs/PROTOCOLS.md) — detect worktree context.
Step 3: Gather Diff
Based on the target, collect the code to review:
- Current:
git diff+git diff --cached - Range:
git diff <range>+git log --oneline <range> - Path:
git diff HEAD -- <path>(or read files directly if untracked) - Branch:
git diff main...<branch>
If the diff is empty, inform the user and stop.
Step 4: Build Agent Context
Assemble context per Agent Context Protocol (see docs/PROTOCOLS.md):
- The diff content collected in Step 3
.shipyard/PROJECT.md(if exists) — for project understanding- Codebase docs per Codebase Docs Protocol (if
.shipyard/exists) - Working directory, current branch, and worktree status
- If a PLAN.md is associated (user mentions a plan), include it for spec compliance review
Step 5: Dispatch Reviewer
Dispatch a reviewer agent (subagent_type: "shipyard:reviewer") with:
- Follow Model Routing Protocol — resolve model from
model_routing.review(default: sonnet) - max_turns: 15
- All context from Step 4
- Instruction: Perform two-stage review (spec compliance if plan provided, otherwise skip to code quality)
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.
- 4d ago First seen · 77 lines · 16 tokens per session scan A 4c351af29d17
review is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 695 once invoked, about $0.0001 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-init
Project setup. Creates constitution and charter. Configures gates.
sw-doctor
Read-only installation health check with repair hints.
sw-guard
Detect stack and configure deterministic guardrails.
sw-status
Show current Specwright state and progress.
sw-pivot
Research-backed rebaselining for planning, building, or verifying work. Preserves completed and shipped scope while revising remaining design, plan, and in-progress work.
sw-ship
Strategy-aware merge via pull request. If branch-head freshness blocks and policy is rebase or merge, recover in the same run; manual is the fallback and still reruns /sw-verify before /sw-ship.