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/felipeslo/opencode-kit/brainstormgit clone --depth 1 https://github.com/felipeslo/opencode-kitWhat 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.00014 | $0.00462 |
| Opus 5 | $0.00007 | $0.00231 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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 yesterday.
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.
What it actually says
/brainstorm - Structured Idea Exploration
$ARGUMENTS
Purpose
This command activates BRAINSTORM mode for structured idea exploration. Use when you need to explore options before committing to an implementation.
Behavior
When /brainstorm is triggered:
-
Understand the goal
- What problem are we solving?
- Who is the user?
- What constraints exist?
-
Generate options
- Provide at least 3 different approaches
- Each with pros and cons
- Consider unconventional solutions
-
Compare and recommend
- Summarize tradeoffs
- Give a recommendation with reasoning
Output Format
## 🧠 Brainstorm: [Topic]
### Context
[Brief problem statement]
---
### Option A: [Name]
[Description]
✅ **Pros:**
- [benefit 1]
- [benefit 2]
❌ **Cons:**
- [drawback 1]
📊 **Effort:** Low | Medium | High
---
### Option B: [Name]
[Description]
✅ **Pros:**
- [benefit 1]
❌ **Cons:**
- [drawback 1]
- [drawback 2]
📊 **Effort:** Low | Medium | High
---
### Option C: [Name]
[Description]
✅ **Pros:**
- [benefit 1]
❌ **Cons:**
- [drawback 1]
📊 **Effort:** Low | Medium | High
---
## 💡 Recommendation
**Option [X]** because [reasoning].
What direction would you like to explore?
Examples
/brainstorm authentication system
/brainstorm state management for complex form
/brainstorm database schema for social app
/brainstorm caching strategy
Key Principles
- No code - this is about ideas, not implementation
- Visual when helpful - use diagrams for architecture
- Honest tradeoffs - don't hide complexity
- Defer to user - present options, let them decide
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.
- yesterday First seen · 114 lines · 14 tokens per session scan A 737f1abb5c3b
brainstorm is a command published in the GitHub repository felipeslo/opencode-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 462 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-31.
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.
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.