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/getappz/agentflare/brainstormingnpx skills add getappz/agentflare --skill brainstorminggit clone --depth 1 https://github.com/getappz/agentflareWrote 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/getappz/agentflare/brainstorming)<a href="https://agentmods.dev/skills/getappz/agentflare/brainstorming"><img src="https://agentmods.dev/badge/skills/getappz/agentflare/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 | $0.00087 | $0.01469 |
| Opus 5 | $0.00044 | $0.00734 |
| Sonnet 5 | $0.00017 | $0.00294 |
| Haiku 4.5 | $0.00009 | $0.00147 |
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 4d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming
Classify a request before touching it, then gate implementation on that
classification. requirements-specification turns an already-concrete ask
into testable requirements; this skill runs before that — while the ask
is still "build me X" or "can we..." and scope isn't pinned down yet.
The gate
The gate is one-way: if a task turns out bigger than its classification mid-work, stop and reclassify upward. Never reclassify downward to skip a step you've already started.
Classify first
State the classification out loud before asking anything else — "this reads as Bounded, so I'll sketch the design in chat rather than write a spec" — so the user can correct it immediately.
- Spike — a feasibility question ("can we...", "is X possible...", "quick and dirty is fine"). The output is an answer, not code to keep. State the question and the 2-3 sentence probe plan, get a nod, then investigate as cheaply as correctness allows. No design doc. Report back as a recommendation; label anything you built as throwaway.
- Bounded — a well-scoped change to a flow that already exists in this repo: a new flag, a small endpoint, a one-file fix. "I understand this kind of app" is not enough — bounded means the code you'd change is already there to read. Ask the clarifying questions that matter, present a short design in chat (a few sentences to a short paragraph: approach, files touched, how you'll verify it), then stop for approval. No spec file.
- Architectural — a new subsystem, a new project, or a change that
restructures how components fit together or alters an interface other
code depends on. Ask clarifying questions, propose 2-3 approaches with
trade-offs and a recommendation, then stop for approval. Once approved,
hand off to
system-architecture-designfor the structural decision and/orrequirements-specificationfor the spec — no implementation plan exists until that handoff's output is itself approved.
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.
- 4d ago First seen · 124 lines · 87 tokens per session scan A de9cadd35767
brainstorming is a skill published in the GitHub repository getappz/agentflare (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 87 tokens to every session and 1,469 once invoked, about $0.0004 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
task-loop
任务目标驱动执行闭环预装 skill,整合任务识别/规划/派发搜推/验收/BBS 接力/arch 场景规划变体(planning-arch)与架构师名册 mock(arch-analysis)共七段为单一 skill,预装到所有 bot 等同各段单独安装到对应 bot;各段按各自触发词自门控仅命中段执行(用户面 /task 或 [RESUMETASK] 或副屏标签命中识别;框架 [planning] 命中规划,arch 场景含「某某某公司」命中 planning-arch 变体;框架 [search] 命中派发搜推;worker 叶子自验收命中验收;引擎 BBS 通知命中接力,其 scoped 叶子 instruction…
bcs-coordination
全场景多智能体协同和交互引擎。覆盖多Bot复杂任务协同与沉浸式娱乐互动。通过提供注册发现、群组构建、上下文融合及路由通信能力等核心能力，支持能力互补、信息和知识的融合、冲突消解、工作流编排，以及2C场景下多人游戏互动等。.
bbs-relay-pickup
被唤醒时从 task API 发现 BBS 升级任务、CAS 占根、自判剩余、挂节点、执行、经回投写回.
bcs-coordination
全场景多智能体协作和交互引擎。覆盖 Bot 注册发现、自由聊天、任务协作、上下文融合、路由通信和自定义协作。用户需要自定义参与角色、执行步骤、串并行关系或最终交付物时，使用自定义协作能力，并通过 BCS 的 statemachine YAML 实现和校验。.
task-planning-arch
计算任务 gap 并产出下一步可执行子任务 List[TaskSpec];gap 已闭返回空数组。对齐 arch 场景(架构师名册/技术栈概览/双视角分析)确定式分解——按根目标交付物集合 + donechildren 查表(参照 task-planning storage 特例,非自由 LLM 分解)。.
task-search
在框架预查的候选 bot 集里决出执行者(who)与协作方式(how),返回 4 态 SearchResult(HITSINGLE/HITGROUP/HITMULTIBOTS/MISS)。对齐案例剧本确定式映射。.