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/plangit 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.00011 | $0.03254 |
| Opus 5 | $0.00005 | $0.01627 |
| Sonnet 5 | $0.00002 | $0.00651 |
| Haiku 4.5 | $0.00001 | $0.00325 |
Grade A, and why
plan 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 3d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:plan - Phase Planning
You are executing the Shipyard planning workflow. Follow these steps precisely.
Step 1: Parse Arguments
- If a phase number is provided, use it.
- If
--skip-researchis provided, skip the research step. - If
--no-discussis provided, skip the discussion capture step. - If
--gapsis provided, this is a gap-filling re-plan (see note at bottom). - If no phase number is provided, read
.shipyard/STATE.jsonto determine the current phase.
Step 1.5: Ensure ROADMAP.md Exists
Check if .shipyard/ROADMAP.md exists.
-
If it exists: Proceed to Step 2.
-
If
.shipyard/PROJECT.mdexists but no ROADMAP.md: Tell the user a roadmap is needed before planning. Dispatch an architect agent (subagent_type:"shipyard:architect") with the full PROJECT.md content to generate.shipyard/ROADMAP.md. Present the roadmap to the user for approval. Allow up to 3 revision cycles where the user can request changes. After approval (or 3 rounds), finalize and proceed to Step 2. -
If neither PROJECT.md nor ROADMAP.md exists: Use
AskUserQuestionto ask: "No project definition or roadmap found. What would you like to do?"Run brainstorming first (Recommended)— Tell the user: "Run/shipyard:brainstormto explore requirements and capture a project definition first." Then stop.Create a minimal roadmap— Ask the user for a brief description of what they want to build. Dispatch an architect agent (subagent_type:"shipyard:architect") with that description to generate.shipyard/ROADMAP.md. Present for approval with up to 3 revision cycles. After approval, proceed to Step 2.Cancel— Stop.
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. - If this phase already has plans and is not a
--gapsrun, ask the user if they want to re-plan (existing plans will be archived).
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.
- 3d ago First seen · 270 lines · 11 tokens per session scan A 1ae030ba8757
plan is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 3,254 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.