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/init)<a href="https://agentmods.dev/commands/lgbarn/shipyard/init"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/init/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/init"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/init.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.00008 | $0.01994 |
| Opus 5.5 | $0.00003 | $0.00798 |
| Sonnet 5.5 | $0.00002 | $0.00399 |
| Haiku 4.5 | $0.00001 | $0.00199 |
Grade A, and why
init 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:init - Project Initialization
You are executing the Shipyard initialization workflow. Follow these steps precisely and in order.
Step 1: Check Existing State
Check if a .shipyard/ directory already exists in the current project root.
-
If it exists AND
.shipyard/config.jsonexists: Read existing config.json values. These become the pre-filled defaults shown in Step 3 (in parentheses after each option). Proceed to Step 2 — the user may want to change any or all settings. -
If
--freshflag is provided: Require explicit confirmation from the user before proceeding. If confirmed, rename.shipyard/to.shipyard-archive-{YYYY-MM-DD}/and create a fresh.shipyard/directory (no pre-filled defaults). If not confirmed, stop. -
If
.shipyard/does not exist: Create the.shipyard/directory and proceed to Step 2.
Step 2: Lightweight Project Detection
Determine whether this is a brownfield (existing source code) or greenfield (empty/new project) by checking for source files and package manifests (e.g., package.json, go.mod, Cargo.toml, requirements.txt, *.py, *.ts, *.go, *.rs, etc.).
Also check if docs/codebase/ exists and contains .md files. If it does, this means a previous /shipyard:map was run and committed — store this as detected_codebase_path = "docs/codebase" for use in Step 4.
This is used to tailor next-steps guidance in Step 5 and to set a smart default for codebase_docs_path — no codebase mapping or analysis is performed.
Step 3: Collect Settings
Collect workflow preferences from the user using three AskUserQuestion calls. Each call stays within the 4-question limit. Wait for the user's answers before proceeding to the next batch.
Batch 1: Workflow Preferences
Use AskUserQuestion with these 3 questions:
- Interaction style — "Do you prefer interactive mode or autonomous mode?"
Interactive (Recommended)— Approve each phase before execution. Safer for unfamiliar codebases.Autonomous— Execute full roadmap with checkpoints. Faster for well-defined projects.
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 · 153 lines · 8 tokens per session scan A 2d6a0ec94f3b
init is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 4d ago), licensed MIT. It adds 8 tokens to every session and 1,994 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.