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/madebytokens/claude-brainstorm/helpgit clone --depth 1 https://github.com/MadeByTokens/claude-brainstormWrote 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/madebytokens/claude-brainstorm/help)<a href="https://agentmods.dev/commands/madebytokens/claude-brainstorm/help"><img src="https://agentmods.dev/badge/commands/madebytokens/claude-brainstorm/help.svg" alt="Measured on agentmods" 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.00013 | $0.01084 |
| Opus 5 | $0.00006 | $0.00542 |
| Sonnet 5 | $0.00003 | $0.00217 |
| Haiku 4.5 | $0.00001 | $0.00108 |
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 6d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Help
The user wants to see help information about the brainstorming plugin. Display a clear, concise reference.
Display Format
Show the following help information:
BRAINSTORM HELP
Commands:
/brainstorm:start [topic] - Start a new brainstorming session
/brainstorm:fork <topic> - Branch into a tangent or sub-topic
/brainstorm:back - Return to parent thread
/brainstorm:status - See current thread, open forks, top ideas
/brainstorm:done - End session with summary
/brainstorm:help - Show this help
Techniques Available:
- Free Association Wild ideas, no filter
- SCAMPER Substitute, Combine, Adapt, Modify, Put to other uses, Eliminate, Reverse
- Six Thinking Hats Facts, Emotions, Caution, Benefits, Creativity, Process
- Reverse Brainstorm "How could we fail?" then flip the answers
- Analogy Hunt Steal solutions from other domains
- Constraint Play "What if no budget?" / "What if infinite time?"
How It Works:
1. Start a session with /brainstorm:start
2. Select one or more techniques
3. Ideas are generated in batches and logged to a session file
4. Fork into tangents anytime, return with /brainstorm:back
5. Claude will suggest forks when promising tangents emerge
6. Claude proactively searches the web for inspiration and analogies
7. End with /brainstorm:done to get a summary
Session Files:
- Full session: brainstorm-[topic]-[timestamp].md
- Summary: brainstorm-[topic]-[timestamp]-summary.md (compact version for follow-up)
- Located in current working directory
After Help
Use the AskUserQuestion tool to offer next steps:
{
"questions": [
{
"question": "What would you like to do?",
"header": "Next",
"multiSelect": false,
"options": [
{"label": "Start brainstorming", "description": "Begin a new session with /brainstorm:start"},
{"label": "Learn more about techniques", "description": "Get detailed explanation of a technique"},
{"label": "Continue", "description": "Go back to what I was doing"}
]
}
]
}
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.
- 6d ago First seen · 124 lines · 13 tokens per session scan A c4fb8f91ab29
help is a command published in the GitHub repository MadeByTokens/claude-brainstorm (13 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 1,084 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.