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/fakoli/fakoli-plugins/brainstormnpx skills add fakoli/fakoli-plugins --skill brainstormgit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/brainstorm)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/brainstorm"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/brainstorm.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.00013 | $0.02202 |
| Opus 5 | $0.00006 | $0.01101 |
| Sonnet 5 | $0.00003 | $0.00440 |
| Haiku 4.5 | $0.00001 | $0.00220 |
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 3d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm — Design Phase
Turn ideas into fully-formed specs through structured dialogue: explore context, assess scope, ask one question at a time, propose approaches, present the design section by section, and hand off to /fakoli-flow:plan.
Process Flow
Start
|
v
[1. Explore project context]
Read CLAUDE.md, project files, recent git log.
Note any output path or naming conventions CLAUDE.md specifies.
|
v
[2. Assess scope]
Does the request describe multiple independent subsystems?
|
YES --> Flag decomposition immediately. Do not ask detailed questions yet.
| Help the user decompose into sub-projects, then brainstorm the first one.
|
NO
|
v
[3. Ask clarifying questions]
One question per message. Multiple choice preferred.
Focus: purpose, constraints, success criteria.
|
v
[4. Auto-detect visual questions]
Is this question about layout, mockups, diagrams, or visual comparison?
|
YES --> Offer visual companion (first time only, its own message).
| If accepted: start server, track PID, serve mockup.
| Subsequent visual questions in the same session reuse the server.
|
NO --> Stay in terminal even if companion is active.
|
v
[5. Propose 2-3 approaches]
Lead with recommendation. Explain trade-offs.
|
v
[6. Present design section by section]
Scale each section to its complexity.
Ask "Does this section look right?" after each one.
Revise before moving forward.
|
v
[7. Write spec]
Save to docs/specs/<YYYY-MM-DD>-<topic>.md
(or the path CLAUDE.md specifies — that path always wins).
|
v
[8. Self-review]
Run the four checks inline. Fix issues before showing the user.
|
v
[9. User reviews spec]
Ask the user to review the file. Wait for explicit approval.
If changes requested: update the file, re-run self-review, re-ask.
|
v
[10. Hand off to /fakoli-flow:plan]
What ships with it
7 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.
- 3d ago First seen · 237 lines · 13 tokens per session scan A 168622b40415
brainstorm is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 25d ago), licensed MIT. It adds 13 tokens to every session and 2,202 once invoked, about $0.0001 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
better-auth-knowledge-patch
Use this skill when implementing, upgrading, debugging, or reviewing Better Auth applications. Start with the quick references below, then load the topic file that matches the task.
clickhouse-knowledge-patch
Use this skill when writing, reviewing, upgrading, or operating ClickHouse SQL and server configurations. Start with the compatibility-sensitive items below, then load the topic reference that matches the task.
arch-knowledge-patch
Restart the daemon immediately after upgrading openssh to 9.8p1 because the old daemon cannot accept new connections.
axum-knowledge-patch
Axum 0.8 uses return-position impl Trait in FromRequestParts and FromRequest. Implement their methods with native async fn; do not retain the old #[asynctrait] annotation.
caddy-knowledge-patch
Use this patch when writing or reviewing Caddyfile or JSON configuration, upgrading Caddy, building custom binaries, or operating Caddy's HTTP, proxy, certificate, and telemetry features.
cloudflare-d1-knowledge-patch
Use this skill when designing, implementing, migrating, operating, or debugging Cloudflare D1 databases. Check the project’s Wrangler configuration, binding usage, database generation, account plan, and remote-versus-local command flags before applying guidance.