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/brainstorm)<a href="https://agentmods.dev/commands/lgbarn/shipyard/brainstorm"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/brainstorm/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/brainstorm"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/brainstorm.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.00011 | $0.01017 |
| Opus 5.5 | $0.00004 | $0.00407 |
| Sonnet 5.5 | $0.00002 | $0.00203 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade A, and why
brainstorm 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:brainstorm - Requirements Exploration
You are executing the Shipyard brainstorming workflow. Follow these steps precisely and in order.
Step 1: Check Project Exists
Verify .shipyard/ directory exists. If not, tell the user:
"No Shipyard project found. Run
/shipyard:initfirst to create a project."
Then stop.
Step 2: Check Existing Project Definition
Check if .shipyard/PROJECT.md already exists.
- If it exists: Use
AskUserQuestionto ask: "A project definition already exists. What would you like to do?"Update existing— Load the current PROJECT.md and use it as starting context for the brainstorming dialogue. The user can refine, expand, or modify the existing definition.Start fresh— Ignore the existing PROJECT.md and begin a new brainstorming session from scratch.
Step 3: Socratic Dialogue
Invoke the shipyard:shipyard-brainstorming skill to conduct a Socratic dialogue with the user.
- Explore what they want to build or change
- Ask clarifying questions about scope, constraints, and priorities
- Identify non-functional requirements (performance, security, accessibility)
- Determine success criteria
- If a topic argument was provided, focus the dialogue on that area
Continue the dialogue until the user indicates they are satisfied with the requirements exploration.
Step 4: Capture Project Definition
When the user is satisfied, capture all decisions into .shipyard/PROJECT.md with these sections:
- Project Name
- Description (1-2 paragraphs)
- Goals (numbered list)
- Non-Goals (explicitly out of scope)
- Requirements (functional, grouped by area)
- Non-Functional Requirements
- Success Criteria
- Constraints (technical, timeline, budget)
Step 5: Offer Roadmap Creation
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 architect model selection.
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 · 108 lines · 11 tokens per session scan A d66d2fe27464
brainstorm is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 1,017 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
harness-init
Initialize a harness for the current project — discover stack, ask about conventions, generate HARNESS.md.
superpowers-init
Full habitat setup — generates CLAUDE.md, HARNESS.md, AGENTS.md, MODELROUTING.md, REFLECTIONLOG.md, agents, CI templates.
question
Read-only code Q&A. Spawns the code-explorer subagent (Haiku-class) to grep, glob, and read excerpts of the codebase, then synthesizes a cited answer with file:line citations. No plan, no gates, no implementation. Fast. Triggers: "where is X defined", "what calls Y", "how does Z work", "find references to", "explain…
sw-audit
Periodic codebase health check for systemic technical debt.
sw-review
PR comment review. Group by status and respond inline.
init
Install the formatters this repository needs, with every command visible before it runs.