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/tommymorgan/claude-plugins/brainstormingnpx skills add tommymorgan/claude-plugins --skill brainstorminggit clone --depth 1 https://github.com/tommymorgan/claude-pluginsWrote 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/tommymorgan/claude-plugins/brainstorming)<a href="https://agentmods.dev/skills/tommymorgan/claude-plugins/brainstorming"><img src="https://agentmods.dev/badge/skills/tommymorgan/claude-plugins/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.00013 | $0.01157 |
| Opus 5 | $0.00006 | $0.00579 |
| Sonnet 5 | $0.00003 | $0.00231 |
| Haiku 4.5 | $0.00001 | $0.00116 |
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 5d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Ideas Into Designs
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
The Process
Phase 1: Understanding the Idea
Check project context first:
- Read relevant files, docs, recent commits
- Understand existing patterns and conventions
- Identify constraints from the codebase
Ask questions one at a time:
- Only one question per message
- Prefer multiple choice questions when possible
- Open-ended questions are fine when choices aren't clear
- Focus on understanding: purpose, constraints, success criteria
Key questions to explore:
- What problem does this solve?
- Who are the users?
- What are the success criteria?
- What are the constraints?
- What already exists that this relates to?
Phase 2: Exploring Approaches
Propose 2-3 different approaches:
- Each approach should be meaningfully different
- Include tradeoffs for each
- Lead with your recommended option
- Explain why you recommend it
Present options conversationally:
I see three ways to approach this:
**Option 1: [Name]** (Recommended)
[Description]
- Pro: [advantage]
- Con: [disadvantage]
**Option 2: [Name]**
[Description]
- Pro: [advantage]
- Con: [disadvantage]
**Option 3: [Name]**
[Description]
- Pro: [advantage]
- Con: [disadvantage]
I recommend Option 1 because [reasoning].
Phase 3: Presenting the Design
Once you understand what to build:
- Break design into sections of 200-300 words
- Before presenting each section to the user, run section-level expert review
- Ask after each section: "Does this section look right?"
- Wait for confirmation before continuing
- Be ready to revise if something doesn't fit
Section-level expert review:
Before the user sees each design section, route it to relevant experts based on content keywords:
| Section Content Keywords | Expert(s) Invoked |
|---|---|
| database, schema, migration, storage, persistence, query | Data Systems Expert |
| page, form, button, display, UI, component, dashboard, click | UX Expert + Accessibility Expert |
| endpoint, request, response, REST, API, HTTP | REST API Guidelines skill + Security Expert |
| deploy, pipeline, build, release, CI/CD, container | Continuous Delivery Expert + Cloud Expert |
| test, spec, scenario, assert, mock, stub, fixture | Testing Expert |
| module, service, boundary, integration, composition, coupling | Software Architecture Expert |
| user, PII, data collection, consent, retention, GDPR | Privacy Expert |
| metric, SLO, monitor, alert, log, trace, observe | SRE Expert |
| domain, entity, aggregate, bounded context, ubiquitous language | Domain Design Expert |
| lead time, deployment frequency, feedback loop, batch size | Engineering Effectiveness Expert |
| (always) | Product Strategy Expert — reviews every section for product value |
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.
- 5d ago First seen · 154 lines · 13 tokens per session scan A d4b30eb9a535
brainstorming is a skill published in the GitHub repository tommymorgan/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,157 once invoked, about $0.0001 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…