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 skills/madappgang/claude-code/brainstormingnpx skills add MadAppGang/claude-code --skill brainstorminggit clone --depth 1 https://github.com/MadAppGang/claude-codeWrote 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/skills/madappgang/claude-code/brainstorming)<a href="https://agentmods.dev/skills/madappgang/claude-code/brainstorming"><img src="https://agentmods.dev/badge/skills/madappgang/claude-code/brainstorming.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.00024 | $0.04490 |
| Opus 5 | $0.00012 | $0.02245 |
| Sonnet 5 | $0.00005 | $0.00898 |
| Haiku 4.5 | $0.00002 | $0.00449 |
Grade B, and why
brainstorming scanned grade B with 1 finding 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
# 3. Configure models in ~/.claude/settings.json How it starts
The opening of the file, as written. The whole thing — 691 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming v2.0: Resilient Multi-Model Planning
Turn ideas into validated designs through collaborative AI dialogue with resilient model execution and confidence-based validation.
Overview
This skill improves upon v1.0 by addressing critical reliability gaps:
Key v2.0 Improvements:
- No AskUserQuestion dependency: Uses Task + Tasks for structured interaction
- Fallback chains: 3+ models per role ensures completion even if some fail
- Explicit parallelism: Documented Task call patterns for parallel execution
- Defined algorithms: Consensus matrix and confidence scoring are mathematically specified
When to Use
Use this skill BEFORE implementing any feature:
- "Design a user authentication system"
- "Brainstorm approaches for API rate limiting"
- "Plan architecture for a new dashboard feature"
- "Evaluate options for real-time data synchronization"
Prerequisites
Required Setup
# 1. Install required skills
/plugin marketplace add MadAppGang/claude-code
skill install superpowers:using-git-worktrees
skill install superpowers:writing-plans
# 2. Verify OpenRouter access (for multi-model)
export OPENROUTER_API_KEY=your-key
# 3. Configure models in ~/.claude/settings.json
{
"brainstorming": {
"primary_model": "anthropic/claude-opus-4-20250514",
"explorer_models": [
"x-ai/grok-code-fast-1",
"google/gemini-2-5-pro",
"anthropic/claude-sonnet-4-20250514"
]
}
}
Model Requirements
| Role | Min Context | Capabilities |
|---|---|---|
| Primary | 200K tokens | Complex reasoning, orchestration |
| Explorer | 100K tokens | Code generation, analysis |
Workflow
Phase 0: Problem Analysis (200-300 words)
Objective: Capture problem scope, constraints, and success criteria
How to Ask Users (Without AskUserQuestion):
// Pattern: Use Tasks to track questions, Read/Write for presentation
// 1. Write question to temp file
await Write({
file_path: "/tmp/brainstorm-q1.md",
content: `## Question 1 of 3
**What are the main constraints or requirements for this feature?**
Please respond with:
- Functional requirements (what it must do)
- Non-functional requirements (performance, scale)
- Any existing dependencies or integrations
`
});
// 2. Present file and wait for user response
// User reads file, provides input via conversation
// 3. Summarize understanding
const problemSummary = await Write({
file_path: "/tmp/brainstorm-problem.md",
content: `## Problem Understanding
**Constraints identified:**
- [From user response]
**Success criteria:**
- [Measurable outcomes]
**Scope boundaries:**
- [What's in/out]
---
**Does this accurately capture the problem?** (Reply "yes" to proceed or clarify)
`
});
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.
- 2d ago First seen · 691 lines · 24 tokens per session scan B 22421ba21144
brainstorming is a skill published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 4,490 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
claude-code-dmwork
Connect to DMWork messaging platform as an AI bot via the OpenClaw DMWork adapter plugin.
meeting
Use for /meeting, /meeting sync, /meeting backfill, or a search term — adaptively analyzes a Granola meeting into decisions, findings, actions, and continuity in shared memory.
project-brainstorming
Guides project ideation via Socratic questioning to produce a validated brief. Use before specification when requirements are unclear.
reflect
Use when the user says 'we decided', 'I realized', or 'that's a pattern' — captures decisions, findings, or patterns in shared memory. Not a private half-baked thought (/note) or cross-referencing (/deep-reflect).
view
Generate a branded HTML artifact from Egregore data (quest, handoff, activity, board, network, or any document) and open it in the browser. Use for /view, 'render this', or 'show me visually'.
dashboard
See your recent sessions, open handoffs, and current work at a glance. Use for /dashboard, checking your personal status — not the team-wide view (/activity).