Borrowing it
Nothing to install: this file belongs to bugrabilge/bilge-development-kit. 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/bugrabilge/bilge-development-kit/main/.claude/skills/brainstorm/SKILL.mdgit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWrote 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/bugrabilge/bilge-development-kit/brainstorm)<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/brainstorm"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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/bugrabilge/bilge-development-kit/brainstorm"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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.00053 | $0.00449 |
| Opus 5.5 | $0.00021 | $0.00180 |
| Sonnet 5.5 | $0.00011 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
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 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.
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.
What it actually says
/brainstorm - Structured Idea Exploration
$ARGUMENTS
Purpose
This command activates BRAINSTORM mode for structured idea exploration. Use when you need to explore options before committing to an implementation.
Behavior
When /brainstorm is triggered:
-
Understand the goal
- What problem are we solving?
- Who is the user?
- What constraints exist?
-
Generate options
- Provide at least 3 different approaches
- Each with pros and cons
- Consider unconventional solutions
-
Compare and recommend
- Summarize tradeoffs
- Give a recommendation with reasoning
Output Format
## Brainstorm: [Topic]
### Context
[Brief problem statement]
---
### Option A: [Name]
[Description]
Pros:
- [benefit 1]
- [benefit 2]
Cons:
- [drawback 1]
Effort: Low | Medium | High
---
### Option B: [Name]
[Description]
Pros:
- [benefit 1]
Cons:
- [drawback 1]
- [drawback 2]
Effort: Low | Medium | High
---
### Option C: [Name]
[Description]
Pros:
- [benefit 1]
Cons:
- [drawback 1]
Effort: Low | Medium | High
---
## Recommendation
**Option [X]** because [reasoning].
What direction would you like to explore?
Key Principles
- No code - this is about ideas, not implementation
- Visual when helpful - use diagrams for architecture
- Honest tradeoffs - don't hide complexity
- Defer to user - present options, let them decide
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 · 109 lines · 53 tokens per session scan A 5a1be223a516
brainstorm is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 6mo ago), licensed MIT. It adds 53 tokens to every session and 449 once invoked, about $0.0002 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…