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/itmisx/deepx-code/brainstormingnpx skills add itmisx/deepx-code --skill brainstorminggit clone --depth 1 https://github.com/itmisx/deepx-codeWhat 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.00064 | $0.00628 |
| Opus 5 | $0.00032 | $0.00314 |
| Sonnet 5 | $0.00013 | $0.00126 |
| Haiku 4.5 | $0.00006 | $0.00063 |
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 2d 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
头脑风暴:先把需求想清楚
移植自 superpowers(MIT)。
硬性闸门
在你拿出一份设计、且用户明确批准之前,不要写任何代码、不要搭脚手架、不要执行任何实现动作。
在 deepx 里可以切到 /plan 模式(Write/Bash 关闭)做只读探索,从机制上挡住"手痒先写"。
流程
按顺序走,别跳:
- 探索上下文。用
Read/Grep/Tree/CodeGraph摸清现有代码与约定,别凭空假设。 - 一次只问一个问题。不要一口气抛一堆问题压垮用户。问完一个,听完回答,再问下一个。
- 提 2–3 种方案,讲清取舍。不要默默选一个就上。把备选摆出来,说明各自的代价。
- 分块呈现设计:目标、模块划分、接口、数据流、边界情况。
- 写下设计文档(可放
docs/下),不要只停留在对话里。 - 自审:设计是否完整?有没有没定的地方?有没有 YAGNI 该砍的?
- 拿用户对"写下来的设计"的批准——不是对口头描述的模糊点头。
- 批准后再动手实现;先把工作拆成小步、每步想清"怎么算成功",再逐步写。拿到批准前不要写代码。
设计原则
- 拆成小单元:每个单元一个清晰职责、通过明确接口通信、能被独立理解和测试。
- 狠心 YAGNI:没要求的功能、没用到的"灵活性"、不可能发生的错误处理——全砍。
- 先提替代再定方案:一上来就锁定单一方案,往往错过更简单的路。
红旗
- 还没拿到批准就开始写代码 / 建文件。
- 一次问用户五个问题。
- 只给一个方案,不讲取舍。
- 设计只在脑子里/对话里,没落成文字就开干。
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.
- 2d ago First seen · 42 lines · 64 tokens per session scan A a16f0aafcb54
brainstorming is a skill published in the GitHub repository itmisx/deepx-code (383 stars, last pushed 7d ago), licensed MIT. It adds 64 tokens to every session and 628 once invoked, about $0.0003 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-30.
Other skills, from other repositories
ai-style
当任务是用中文撰写或改写面向读者的文案（产品发布稿、公众号文章、邮件、README 等）， 或用户反馈文字「AI 味太重」「不像人写的」时，加载本 Skill。.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
data_analysis
基于已确认数据执行可审计的数学计算和描述统计。.
pr-comments
Use when the user asks to review pull request comments, or when the /pr-comments command runs — fetch and analyze PR review comments on the current branch and summarize actionable items.
review
Use when asked to review a codebase or a change, or when the /review command runs — assess design, correctness, maintainability, and test coverage with actionable feedback.
dsh-doc-site-sync
Use when publishing, updating, moving, or removing DeepSeek Harness documentation website pages; editing website/docs.ts mappings or navigation; diagnosing a page missing from the VitePress site; fixing projected documentation links; or running the docs:dev, docs:check, and doc-sync workflow after website-content…