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/rafaelkamimura/claude-tools/brainstormgit clone --depth 1 https://github.com/rafaelkamimura/claude-toolsWrote 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/rafaelkamimura/claude-tools/brainstorm)<a href="https://agentmods.dev/commands/rafaelkamimura/claude-tools/brainstorm"><img src="https://agentmods.dev/badge/commands/rafaelkamimura/claude-tools/brainstorm.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 | $0.00000 | $0.02767 |
| Opus 5 | $0.00000 | $0.01384 |
| Sonnet 5 | $0.00000 | $0.00553 |
| Haiku 4.5 | $0.00000 | $0.00277 |
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 3d 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 — 514 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm Session
Deep thinking command for exploring implementation ideas, analyzing possibilities, and capturing creative solutions with context preservation.
Purpose
- Ultra-deep analysis of implementation ideas
- Interactive requirement gathering
- Possibility and feasibility exploration
- Context preservation for future reference
- Transition to implementation when ready
Workflow
Phase 1: Session Initialization
-
STOP → "What would you like to brainstorm about?"
- Wait for user to provide initial concept/idea
-
Generate Session ID
# Create unique session identifier timestamp=$(date +%Y%m%d_%H%M%S) session_id="bs_${timestamp}" # Extract short description from prompt description=$(echo "$prompt" | head -c 30 | tr ' ' '-' | tr -cd '[:alnum:]-') filename="brainstorm-${description}" -
Save Initial Prompt
mkdir -p .claude/brainstorms echo "# Brainstorm: $prompt" > .claude/brainstorms/${filename}.md echo "**Session ID**: $session_id" >> .claude/brainstorms/${filename}.md echo "**Date**: $(date)" >> .claude/brainstorms/${filename}.md echo "**Status**: Active" >> .claude/brainstorms/${filename}.md
Phase 2: Ultra-Deep Thinking Mode
-
Activate Deep Analysis Deploy specialized agents for comprehensive analysis:
- backend-architect: System design implications
- frontend-developer: UI/UX considerations
- database-optimizer: Data structure needs
- security-auditor: Security implications
- performance-engineer: Performance considerations
- test-automator: Testing strategies
-
Multi-Dimensional Analysis
ULTRA-THINK DIMENSIONS: 1. Technical Feasibility - Architecture patterns - Technology stack options - Integration points - Scalability considerations 2. Implementation Complexity - Time estimates - Resource requirements - Skill dependencies - Risk factors 3. Business Impact - User value - Performance implications - Maintenance burden - Cost-benefit analysis 4. Alternative Approaches - Different solutions - Trade-offs - Hybrid approaches - Incremental paths
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.
- 3d ago First seen · 514 lines · 0 tokens per session scan A 1085a6d6a819
brainstorm is a command published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,767 tokens. 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
git
Git operations with intelligent commit messages and workflow optimization.
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.