Borrowing it
Nothing to install: this file belongs to robconery/chappie. 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/robconery/chappie/main/.claude/skills/brainstorming/SKILL.mdgit clone --depth 1 https://github.com/robconery/chappieWrote 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/robconery/chappie/brainstorming)<a href="https://agentmods.dev/skills/robconery/chappie/brainstorming"><img src="https://agentmods.dev/badge/skills/robconery/chappie/brainstorming/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/skills/robconery/chappie/brainstorming"><img src="https://agentmods.dev/badge/skills/robconery/chappie/brainstorming.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.00067 | $0.02095 |
| Opus 5.5 | $0.00027 | $0.00838 |
| Sonnet 5.5 | $0.00013 | $0.00419 |
| Haiku 4.5 | $0.00007 | $0.00210 |
Grade A, and why
brainstorming scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **API**: `curl` returns expected status and response shape How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running a structured brainstorming session for a new feature. Follow each phase in order. Do not skip phases. Do not rush to solutions.
Rules
Always as one question at a time!
Phase 1: Explore
Before asking anything, think out loud about the feature. Consider:
- What problem does it solve and for whom?
- What are the edges, exceptions, and failure modes?
- What existing code or systems does it touch?
- What could go wrong technically and from a user perspective?
- What might the user not have considered?
Write this exploration out — 3 to 5 paragraphs. Be lateral. Surface non-obvious concerns.
Phase 2: Clarify (3 rounds, one at a time)
Ask clarifying questions to extract detail about both the feature intent and the implementation.
Rules — do not break these:
- Ask exactly one question. Not two. Not a question with sub-bullets. One.
- Stop. Wait for the answer. Do not continue until the user replies.
- Then ask the next single question. Repeat for 3 rounds total.
After all 3 rounds, summarize what you now understand.
Phase 3: Propose (3 rounds, one at a time)
Offer a distinct solution approach. Include:
- The core idea in 2-3 sentences
- Key tradeoffs (what it's good at, what it sacrifices)
- Any notable implementation risks
After presenting, ask: "Want to explore this further, see the next option, or change direction?"
Wait for the user's response before the next round. The user may steer, combine approaches, or call it early.
Phase 4: Verification Design
For the agreed approach, propose specific, deterministic verification steps — one per task that will be in the plan.
Each verification must be:
- A shell command or script that exits
0on success, non-zero on failure - Runnable without Claude's involvement
- Specific enough to actually catch regressions
Examples by context:
- Web app:
npm run buildexits 0;agent-browsersnapshot confirms a key element is present - API:
curlreturns expected status and response shape - Data processing: row count matches expected value, column sum within tolerance
- CLI tool: command runs without error and output matches a fixture
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 · 270 lines · 67 tokens per session scan A 44e5be6e33ef
brainstorming is a skill published in the GitHub repository robconery/chappie (11 stars, last pushed 6mo ago), licensed MIT. It adds 67 tokens to every session and 2,095 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…