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/help)<a href="https://agentmods.dev/commands/lgbarn/shipyard/help"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/help/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/help"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/help.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.01403 |
| Opus 5.5 | $0.00003 | $0.00561 |
| Sonnet 5.5 | $0.00002 | $0.00281 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade A, and why
help 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:help - Quick Reference & Help
You are executing the Shipyard help command. Follow these steps precisely.
Step 1: Check for Topic Argument
If a topic argument was provided (e.g., /shipyard:help build), skip to Step 3.
If no argument was provided, show the default quick-reference table (Step 2).
Step 2: Default — "I Want To..." Quick Reference
Display this table:
Shipyard Quick Reference
═══════════════════════════════════════════
I Want To... Command
─────────────────────────────────────────────
Set up a new project /shipyard:init
Explore requirements /shipyard:brainstorm
Understand existing code /shipyard:map
Plan a phase /shipyard:plan [phase]
Build from a plan /shipyard:build [phase]
Quick one-off task /shipyard:quick "task"
Review my code /shipyard:review
Security check /shipyard:audit
Research technology options /shipyard:research "topic"
Find duplication/complexity /shipyard:simplify [scope]
Generate documentation /shipyard:document [scope]
Run tests and verify /shipyard:verify [criteria]
Check progress /shipyard:status
Change settings /shipyard:settings
Rollback to checkpoint /shipyard:rollback
Recover from errors /shipyard:recover
Ship completed work /shipyard:ship
Then display:
"For detailed help on a specific command or skill, run
/shipyard:help <topic>." "Example:/shipyard:help buildor/shipyard:help tdd"
Stop here.
Step 3: Topic-Specific Help
Match the topic argument to a command or skill:
Command Topics
| Topic | Maps To |
|---|---|
init |
/shipyard:init — Set up project preferences (interaction mode, git strategy, quality gates) |
brainstorm |
/shipyard:brainstorm — Socratic dialogue exploring goals/constraints, produces PROJECT.md |
import-spec |
/shipyard:import-spec <feature-path> — Import a spec-kit feature spec (replaces brainstorm) |
import-spec-file |
/shipyard:import-spec-file <path> — Import a handwritten spec file; interviews to fill gaps |
plan |
/shipyard:plan [phase] — Research + architect + verify agents create executable plans |
build |
/shipyard:build [phase] — Builder agents per plan + two-stage review + security audit |
ship |
/shipyard:ship — Verification + tests + audit + docs + delivery options |
status, s |
/shipyard:status — Progress dashboard with next-action routing |
resume |
/shipyard:resume — Reconstruct context and resume interrupted work |
settings |
/shipyard:settings — View/update config preferences |
quick, q |
/shipyard:quick "task" — Architect + builder for small tasks |
review |
/shipyard:review — Two-stage code review (spec + quality) |
audit |
/shipyard:audit — OWASP + secrets + dependencies + IaC security |
simplify |
/shipyard:simplify — Detect duplication, dead code, over-engineering |
document |
/shipyard:document — Generate API docs, architecture, user guides |
research |
/shipyard:research "topic" — Evaluate technology options |
verify |
/shipyard:verify — Run acceptance criteria, record evidence |
map |
/shipyard:map — Deep codebase analysis (up to 7 docs) |
issues |
/shipyard:issues — Manage deferred issues with severity tracking |
rollback |
/shipyard:rollback — Revert to a git checkpoint |
recover |
/shipyard:recover — Diagnose and fix state inconsistencies |
worktree |
/shipyard:worktree — Git worktree management |
doctor |
/shipyard:doctor — Check plugin health and dependencies |
cancel |
/shipyard:cancel — Pause in-progress work with checkpoint |
help |
/shipyard:help — This help command |
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 · 119 lines · 8 tokens per session scan A 6e8d5f694a45
help 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,403 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.