Borrowing it
Nothing to install: this file belongs to pproenca/agent-tui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pproenca/agent-tui/master/.claude/commands/brainstorm.mdgit clone --depth 1 https://github.com/pproenca/agent-tuiWrote 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/pproenca/agent-tui/brainstorm)<a href="https://agentmods.dev/commands/pproenca/agent-tui/brainstorm"><img src="https://agentmods.dev/badge/commands/pproenca/agent-tui/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/pproenca/agent-tui/brainstorm"><img src="https://agentmods.dev/badge/commands/pproenca/agent-tui/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.00009 | $0.01065 |
| Opus 5.5 | $0.00004 | $0.00426 |
| Sonnet 5.5 | $0.00002 | $0.00213 |
| Haiku 4.5 | $0.00001 | $0.00106 |
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 2mo 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm Command
Facilitate a structured brainstorming session and capture raw ideas into a discoverable artifact.
Artifact Location
All brainstorming artifacts are stored in: .claude/specs/<feature-name>/brainstorm.md
This location is used by downstream commands:
/spec <feature-name>reads from here to create formal specification/plan-tdd <feature-name>can read the full chain
Execution Flow
Step 1: Setup
Extract feature name from argument: $ARGUMENTS
If no argument provided, use AskUserQuestion:
What feature or idea do you want to brainstorm?
- Short name (e.g., "plugin-system", "auth-flow", "real-time-sync")
Create directory: .claude/specs/<feature-name>/
Step 2: Context Gathering
Optionally explore the codebase to ground the brainstorm:
Use AskUserQuestion:
Should I explore the codebase first to understand relevant context?
○ Yes - explore architecture and patterns (Recommended)
○ No - start with blank slate
If yes, use Task tool with subagent_type=Explore to understand:
- Current architecture relevant to the feature
- Similar patterns already in codebase
- Potential integration points
Step 3: Structured Brainstorming
Guide the user through these dimensions using AskUserQuestion and conversation:
3.1 Problem Space
Ask and capture:
- What problem are we solving?
- Who experiences this problem?
- What's the impact of not solving it?
- Are there workarounds today?
3.2 Solution Space
Ask and capture:
- What's the ideal end state?
- What are possible approaches?
- What similar solutions exist (in this codebase or elsewhere)?
- What are the trade-offs between approaches?
3.3 Constraints
Ask and capture:
- Technical constraints (performance, compatibility, dependencies)
- Business constraints (timeline, resources, scope)
- User constraints (learning curve, migration path)
3.4 Risks & Unknowns
Ask and capture:
- What could go wrong?
- What don't we know yet?
- What needs prototyping or research?
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.
- 2mo ago First seen · 221 lines · 9 tokens per session scan A e846e7077153
brainstorm is a command published in the GitHub repository pproenca/agent-tui (122 stars, last pushed 8d ago), licensed MIT. It adds 9 tokens to every session and 1,065 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
brain-stats
Show claudectl brain learning metrics — accuracy, correction rate, and effectiveness.
safe-build
Build the application for development or production.
nab
Fetch, archive, or research URLs with nab.
jdi-handoff
Hand this session off to an unattended agent-jdi run (quits it, then resumes in the background).
check
Audit a .nika workflow before it runs — findings with their NIKA-XXXX codes, cost envelope, permits.
trace
Inspect a Nika run's result, trace integrity and recovery evidence.