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/ao92265/claude-code-playbook/brainstormingnpx skills add ao92265/claude-code-playbook --skill brainstorminggit clone --depth 1 https://github.com/ao92265/claude-code-playbookWrote 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/ao92265/claude-code-playbook/brainstorming)<a href="https://agentmods.dev/skills/ao92265/claude-code-playbook/brainstorming"><img src="https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/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.1 | $0.00148 | $0.01048 |
| Opus 5 | $0.00074 | $0.00524 |
| Sonnet 5 | $0.00030 | $0.00210 |
| Haiku 4.5 | $0.00015 | $0.00105 |
Grade A, and why
brainstorming 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 6d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming
Step 1: Assess Trigger Conditions
Check whether this skill applies. Proceed if any of the following are true:
- The user has a vague idea to flesh out.
- The user is planning a new feature or project.
- The user is working through a problem with multiple valid approaches.
- The user said "help me think through", "brainstorm", "explore this idea", "design", or "figure out how to".
- Implementation has not yet started.
If none apply, do not activate this skill.
Step 2: Gather Project Context
- Identify the current project from
$CWDor conversation context. - Determine what already exists: relevant files, modules, patterns, constraints.
- If the project context is unclear, ask one targeted question to establish it before proceeding.
Step 3: Clarify the Idea (One Question at a Time)
Ask clarifying questions sequentially — never more than one at a time. Use the following priority order, stopping when the answer is clear:
- What problem does this solve?
- Who benefits from this?
- What constraints exist (time, tech stack, compatibility)?
- What has already been tried?
If the user's framing contains a questionable assumption, surface it explicitly: "This assumes X — is that correct?" Wait for confirmation before proceeding.
If multiple valid interpretations of the request exist, present them as numbered another-projectns and ask the user to select one. Do not pick silently.
Step 4: Propose 2–3 Alternative Approaches
Do not validate the first idea uncritically. Generate 2–3 distinct approaches and present each using this format:
Option A: [Name]
- Approach: [How it works]
- Pros: [Benefits]
- Cons: [Drawbacks]
- Best when: [Ideal use case]
For each another-projectn, identify at least one risk or failure mode ("What could go wrong?").
Actively challenge scope: if any proposed feature is speculative or not clearly needed, flag it and recommend removal.
Step 5: Confirm Direction
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.
- 6d ago First seen · 130 lines · 148 tokens per session scan A be33736b12c3
brainstorming is a skill published in the GitHub repository ao92265/claude-code-playbook (10 stars, last pushed 19d ago), licensed MIT. It adds 148 tokens to every session and 1,048 once invoked, about $0.0007 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…