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/oborchers/fractional-ctoWrote 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/oborchers/fractional-cto/brainstorm)<a href="https://agentmods.dev/commands/oborchers/fractional-cto/brainstorm"><img src="https://agentmods.dev/badge/commands/oborchers/fractional-cto/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/oborchers/fractional-cto/brainstorm"><img src="https://agentmods.dev/badge/commands/oborchers/fractional-cto/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.00017 | $0.00793 |
| Opus 5.5 | $0.00007 | $0.00317 |
| Sonnet 5.5 | $0.00003 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00079 |
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 5d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply structured brainstorming to the given problem using the structured-brainstorming skill.
Follow this process:
Step 1: Problem Capture
If no problem statement was provided as an argument, ask the user to describe the problem they want to brainstorm.
Step 2: Problem Restatement
Restate the problem in your own words: what is being decided, what constraints exist, and what a good outcome looks like. Present this restatement to the user.
Step 3: Dispatch or Rephrase
Use AskUserQuestion to ask the user how to proceed:
- Dispatch brainstorm-explorer agents — launch parallel agents to explore the problem from multiple angles using structured thinking methods
- Rephrase the problem statement — iterate on the problem framing before committing to exploration
If the user chooses to rephrase, they provide a new or refined problem statement. Return to Step 2 with the updated statement. This loop can repeat until the user is satisfied with the framing.
Step 4: Method Selection and Agent Assignment
Select methods from the method selection table in the structured-brainstorming skill based on the problem type. Assign methods to 4 brainstorm-explorer agents following the agent dispatch pattern in the skill. Present the dispatch plan (which agent gets which methods) as information — the model selects methods to maximize exploration variance.
Step 5: Agent Dispatch
Spawn 4 brainstorm-explorer subagents in parallel. Each agent receives:
- The problem statement
- Its assigned methods (1-2 per agent)
- Instructions to read the relevant method reference files from the skill
Step 6: Synthesis
After all agents complete, synthesize their findings into the standard output structure:
- Problem restatement — the confirmed problem framing
- Method application — labeled sections showing each agent's findings per method
- Convergence — where methods agree, disagree, and surprise
- Recommendation — concrete next step(s) with explicit trade-offs
- Open questions — what remains uncertain and how to resolve it
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.
- 5d ago First seen · 74 lines · 17 tokens per session scan A 75d9a3e30248
brainstorm is a command published in the GitHub repository oborchers/fractional-cto (32 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 793 once invoked, about $0.0001 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-10-13.
Other commands, from other repositories
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.