Borrowing it
Nothing to install: this file belongs to fulminate-io/knowledge-mcp. 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/fulminate-io/knowledge-mcp/main/.claude/skills/brainstorm/SKILL.mdgit clone --depth 1 https://github.com/fulminate-io/knowledge-mcpWrote 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/fulminate-io/knowledge-mcp/brainstorm)<a href="https://agentmods.dev/skills/fulminate-io/knowledge-mcp/brainstorm"><img src="https://agentmods.dev/badge/skills/fulminate-io/knowledge-mcp/brainstorm/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/fulminate-io/knowledge-mcp/brainstorm"><img src="https://agentmods.dev/badge/skills/fulminate-io/knowledge-mcp/brainstorm.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.00073 | $0.01865 |
| Opus 5.5 | $0.00029 | $0.00746 |
| Sonnet 5.5 | $0.00015 | $0.00373 |
| Haiku 4.5 | $0.00007 | $0.00186 |
Grade A, and why
brainstorm 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 1mo 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm: $ARGUMENTS
Active role: peer collaborator with the user. The deliverable is a validated ticket. When the ticket is validated the session switches to /orchestrate.
The ticket is the one artifact no later audit can correct. Time spent here is the cheapest time in the pipeline.
MANDATED READS (stamp each as read: <file> v<N> on the ticket)
| When | Read |
|---|---|
| First action, before any tool call | .claude/skills/GOVERNANCE.md |
| Before drafting the ticket | .claude/skills/ticket/SKILL.md |
| Before any spawn | .claude/skills/write-a-brief/SKILL.md |
Step 0: Recall
thoughts({"operation":"recall","mode":"context","query":"<topic keywords>"})
and search over the knowledge graph for decisions, findings, tickets and
prior thoughts on the topic. Present what the graph already knows before
saying anything about the topic yourself: a prior decision binds until the
user changes it; a prior finding is a lead to reproduce, not a fact.
Then manage({"operation":"status"}); if the index is behind, collect.
Step 1: The assumption ledger
Write the framing's load-bearing assumptions as a thought, each marked UNVERIFIED, with existence claims flagged ("there is no X", "we need to build Y"). Existence defaults to "it already exists" until disproven; the burden of proof is on absence.
Step 2: Research what exists
Spawn a researcher in discovery mode, in the background, with a discovery
brief: how does this repository or the platform already solve this class of
problem, with the existing idiom named and the call graph around the key
symbols. Never name a solution in the brief. Draft with the user while it
runs; when it returns, fold what exists into the conversation and update the
ledger.
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.
- 1mo ago Changed 129e76a758c5
- 1mo ago Changed · -480 lines · +24 tokens per session b7bc5a6d113c
- 2mo ago First seen · 645 lines · 49 tokens per session scan A 152014118612
brainstorm is a skill published in the GitHub repository fulminate-io/knowledge-mcp (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 73 tokens to every session and 1,865 once invoked, about $0.0003 per session on Opus 5.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
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…