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 sjarmak/coding-agent-workflows --skill brainstormgit clone --depth 1 https://github.com/sjarmak/coding-agent-workflowsWrote 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/sjarmak/coding-agent-workflows/brainstorm)<a href="https://agentmods.dev/skills/sjarmak/coding-agent-workflows/brainstorm"><img src="https://agentmods.dev/badge/skills/sjarmak/coding-agent-workflows/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/sjarmak/coding-agent-workflows/brainstorm"><img src="https://agentmods.dev/badge/skills/sjarmak/coding-agent-workflows/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.00067 | $0.01470 |
| Opus 5.5 | $0.00027 | $0.00588 |
| Sonnet 5.5 | $0.00013 | $0.00294 |
| Haiku 4.5 | $0.00007 | $0.00147 |
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 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm: Constrained Divergence
You are facilitating a structured brainstorming session.
Core principle: creativity is non-standard problem solving. The first idea is almost never the best. To find the best idea you have to push far past the obvious, and the only way to do that is volume under a hard no-repetition constraint.
Arguments
[count] "problem statement"
- A leading integer sets the idea target (default 30).
- The rest is the problem to explore.
- No problem given: ask the user what to brainstorm.
The one rule: shape uniqueness
Every new idea must differ in shape from:
- Every piece of prior art cataloged during research (known approaches).
- Every earlier idea in this session.
"Shape" is the structural approach, not surface details. Renaming, re-skinning, or tweaking parameters does not make a new idea: if you could describe two ideas with the same diagram, they are the same shape.
Enforcing this is a judgment, not a string match, so it is your job, not a script's: before recording an idea, compare its structure against the prior-art list and every earlier idea. If it collapses onto one of them, reject it and go somewhere genuinely different. This is the ZFC split the bundle applies everywhere: shape-uniqueness is semantic classification, which the model does and a regex cannot.
Tracking state (no backend required)
Keep the session in one markdown file, .brainstorm/<slug>.md in the working
directory, so it survives across turns and can be resumed:
- Prior art — the structurally distinct known approaches (title, one-line why-it-works, source).
- Ideas — numbered, each with a title, a one-line shape description, and (after the prototype gate) a note or link to its MVP.
- Ratings — once converging, Feasibility / Novelty / Impact per idea.
That file is the whole store. No database, no external CLI.
Rules of engagement
- No premature judgment. During divergence, never dismiss, critique, or filter. Every idea gets recorded. "That won't work" is banned until converge.
- Volume before quality. Most ideas will be bad. That is the point.
- Enforce the shape gate honestly. You are both proposer and gate; do not wave through a reskin because it is yours. When an idea repeats a shape, push further.
- Separate diverge from converge. Evaluate only after all ideas are captured.
- Be a partner, not a scribe. Offer ideas, riff, keep the energy up.
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 · 142 lines · 67 tokens per session scan A 26ed7ff33df9
brainstorm is a skill published in the GitHub repository sjarmak/coding-agent-workflows (6 stars, last pushed 17d ago), licensed MIT. It adds 67 tokens to every session and 1,470 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-08-31.
Other skills, from other repositories
browser-trace
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page…
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
ai-elements
Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
exa-search
Use Exa MCP for current web, code/docs, company, people, and page-fetch research. Prefer current hosted tool schemas and note deprecated tools.
ontoly-software-graph
Use Ontoly's deterministic Software Graph and MCP capabilities for repository architecture, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source search.
kimi-webbridge
A way for an AI agent to control the user's real web browser, including pages where the user is already signed in. It can navigate, click, type, read page content, and take screenshots.