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 skills add XRenSiu/claude-code-forge --skill brainstorminggit clone --depth 1 https://github.com/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/brainstorming)<a href="https://agentmods.dev/skills/xrensiu/claude-code-forge/brainstorming"><img src="https://agentmods.dev/badge/skills/xrensiu/claude-code-forge/brainstorming/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/xrensiu/claude-code-forge/brainstorming"><img src="https://agentmods.dev/badge/skills/xrensiu/claude-code-forge/brainstorming.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.00078 | $0.01575 |
| Opus 5.5 | $0.00031 | $0.00630 |
| Sonnet 5.5 | $0.00016 | $0.00315 |
| Haiku 4.5 | $0.00008 | $0.00158 |
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 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Skill
核心原则
在写任何代码前，通过结构化对话验证需求和方案。
这个 Skill 防止的认知陷阱：收到需求后立即开始写代码，导致产出与预期偏差、大量返工。
何时使用
digraph {
rankdir=TB;
start [label="收到任务" shape=oval];
q1 [label="需要设计\n新东西?" shape=diamond];
q2 [label="修改核心\n行为?" shape=diamond];
q3 [label="有多种\n可能方案?" shape=diamond];
use [label="使用此 Skill" shape=box style=filled fillcolor=lightgreen];
skip [label="不需要" shape=box];
start -> q1;
q1 -> use [label="是"];
q1 -> q2 [label="否"];
q2 -> use [label="是"];
q2 -> q3 [label="否"];
q3 -> use [label="是"];
q3 -> skip [label="否"];
}
流程
阶段 1：侦察（静默执行，不输出）
在问任何问题之前，先：
- 阅读相关代码/文档，理解现有架构
- 识别受影响的模块和依赖
- 找出现有的设计模式和约定
不允许在侦察前提问。 侦察结果决定问题的质量。
阶段 2：发散探索
使用创意激发工具扩展可能性：
| 工具 | 用法 | 适用场景 |
|---|---|---|
| SCAMPER | 替代/组合/调整/修改/挪用/消除/重排 | 改进现有功能 |
| 约束反转 | 如果 [限制] 不存在会怎样？ | 突破思维定式 |
| 类比迁移 | X 领域如何解决类似问题？ | 寻找新视角 |
探索 2-3 个显著不同的方案，不要过早收敛。
阶段 3：提问（每次只问一个）
规则：
- 每次只问一个问题，等待回答后再问下一个
- 做推荐：「我建议 X，因为 Y。这样可以吗？」
- 提供选项：给出 2-3 个选项时标注推荐项
示例：
✅ "我建议用 React Query 管理状态，因为项目已有这个依赖且能自动处理缓存。可以吗？"
❌ "你想用什么状态管理？要支持离线吗？性能要求是什么？"
阶段 4：收敛呈现（分块输出）
呈现设计方案时：
- 每块 200-300 字
- 等待明确确认后才继续
- 应用 YAGNI 原则：只设计当前需要的
输出结构：
- 问题定义（一句话）
- 推荐方案 + 理由
- 被否决的替代方案（简述为何否决）
- 关键技术决策
- 风险和缓解措施
阶段 5：文档
使用模板 templates/design-doc.md，保存到：docs/designs/YYYY-MM-DD-<topic>.md
文档必须包含：
- 完整的需求澄清记录（问题 + 回答 + 决策影响）
- 推荐方案及否决方案
- 明确的范围边界（In Scope / Out of Scope）
- 可测量的成功指标
- 开放问题（如有）
阶段 6：交接
完成后：
- 确认设计文档已保存
- 输出交接提示：
✅ 需求澄清完成 📄 设计文档: docs/designs/YYYY-MM-DD-<topic>.md 📋 下一步选择: • 生成 PRD: /prd docs/designs/<file>.md - 不要自行开始写代码或生成 PRD
反模式
| 坏行为 | 为什么失败 | 正确做法 |
|---|---|---|
| 一次问多个问题 | 用户挑简单的答，跳过复杂的 | 每次一个 |
| 跳过侦察直接问 | 问题通用且无关 | 先读代码再问 |
| 一次性输出完整设计 | 用户草草确认「应该没问题」 | 分块 200-300 字 |
| 推卸判断给用户 | 浪费人类时间 | 做推荐 |
| 过早收敛到第一个方案 | 错过更好的可能性 | 先发散后收敛 |
| 澄清完直接写代码 | 跳过 PRD 导致任务分解混乱 | 必须先生成 PRD |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 168 lines · 78 tokens per session scan A 76704f518799
brainstorming is a skill published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It adds 78 tokens to every session and 1,575 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-09-05.
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…