Borrowing it
Nothing to install: this file belongs to moberghr/mtk-agent-toolkit. 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/moberghr/mtk-agent-toolkit/main/.claude/skills/brainstorming/SKILL.mdgit clone --depth 1 https://github.com/moberghr/mtk-agent-toolkitWrote 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/moberghr/mtk-agent-toolkit/brainstorming)<a href="https://agentmods.dev/skills/moberghr/mtk-agent-toolkit/brainstorming"><img src="https://agentmods.dev/badge/skills/moberghr/mtk-agent-toolkit/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.00029 | $0.01754 |
| Opus 5 | $0.00015 | $0.00877 |
| Sonnet 5 | $0.00006 | $0.00351 |
| Haiku 4.5 | $0.00003 | $0.00175 |
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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming
Overview
Explore the design space before committing to a single approach. Brainstorming produces 2-3 concrete alternatives with explicit tradeoffs, then converges on an approved direction. This phase prevents the most expensive mistake: building the wrong thing correctly.
When To Use
- The engineer says "how should we..." or "what's the best way to..."
- Multiple implementation approaches are plausible
- The task involves architectural decisions with long-term consequences
- The scope or requirements are ambiguous
- Before spec-driven-development when the design direction is not obvious
When NOT To Use
- The approach is already clear and agreed upon
- The task is a bug fix, config change, or narrow refactor
- The engineer explicitly says "just do it this way"
Workflow
-
Explore context before proposing anything:
- Read
CLAUDE.mdand.claude/references/architecture-principles.md(if present) - Read existing code in the affected area
- Check recent git history for relevant decisions or attempts
- Understand current constraints (tech stack, patterns, conventions)
- Read
-
Ask clarifying questions one at a time:
- Focus on constraints that would eliminate approaches
- Ask about non-functional requirements (performance, compatibility, timeline)
- Ask about user/caller expectations
- Stop asking when you have enough to differentiate approaches
-
Propose 2-3 concrete approaches with this structure for each:
- Approach name — one-line summary
- How it works — concrete description with file/component names
- Pros — specific advantages for this codebase
- Cons — specific risks, costs, or limitations
- Effort — relative complexity (files touched, new abstractions needed)
- Fits when — the conditions under which this approach is the best choice
-
Present a recommendation with reasoning:
- Which approach you'd pick and why
- What would change your recommendation
- Risks of the recommended approach and how to mitigate them
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 · 158 lines · 29 tokens per session scan A dfbc7ec0e4f4
brainstorming is a skill published in the GitHub repository moberghr/mtk-agent-toolkit (7 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 1,754 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…
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…