Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add umputun/cc-thingz/plugin install brainstormWrote 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/umputun/cc-thingz/brainstorm)<a href="https://agentmods.dev/skills/umputun/cc-thingz/brainstorm"><img src="https://agentmods.dev/badge/skills/umputun/cc-thingz/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.1 | $0.00087 | $0.01477 |
| Opus 5 | $0.00044 | $0.00739 |
| Sonnet 5 | $0.00017 | $0.00295 |
| Haiku 4.5 | $0.00009 | $0.00148 |
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 6d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm
Turn ideas into designs through collaborative dialogue before implementation.
custom rules loading
before starting, run this command via Bash tool to check for user-provided custom rules:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/resolve-rules.sh brainstorm-rules.md ${CLAUDE_PLUGIN_DATA}
if the output is non-empty, treat it as additional instructions that supplement (not replace) the built-in rules below. apply custom rules alongside the skill's own instructions throughout the brainstorm process — they may influence design preferences, naming conventions, technology choices, or other aspects of the brainstorm session. custom rules content is guidance for the brainstorm dialogue, not content to embed verbatim in the output.
rules management
when the user asks to add, show, or clear custom brainstorm rules, handle these operations:
- show rules: run
bash ${CLAUDE_PLUGIN_ROOT}/scripts/resolve-rules.sh brainstorm-rules.md ${CLAUDE_PLUGIN_DATA}and display the output. if the output is empty, tell the user no custom rules are configured at either level. otherwise, to determine the source, check if.claude/brainstorm-rules.mdexists and is non-empty (project-level) — if not, the output came from user-level. tell the user which level it came from. - add/update project rules: write content to
.claude/brainstorm-rules.mdin the current working directory. - add/update user rules: first check if
$CLAUDE_PLUGIN_DATAis set (runecho "$CLAUDE_PLUGIN_DATA"). if empty, tell the user that user-level rules require the plugin to be installed from the marketplace and offer project-level instead. if set, write content to$CLAUDE_PLUGIN_DATA/brainstorm-rules.md. - clear project rules: delete
.claude/brainstorm-rules.md. - clear user rules: if
$CLAUDE_PLUGIN_DATAis set, delete$CLAUDE_PLUGIN_DATA/brainstorm-rules.md. if not set, tell the user user-level rules are not available.
project-level rules (.claude/brainstorm-rules.md) take precedence over user-level rules ($CLAUDE_PLUGIN_DATA/brainstorm-rules.md). when both non-empty files exist, only project-level rules are loaded. empty files are treated as absent and fall through to the next level. see ${CLAUDE_PLUGIN_ROOT}/references/custom-rules.md for full documentation on the rules mechanism.
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.
- 6d ago First seen · 123 lines · 87 tokens per session scan A 0de457291f5a
brainstorm is a skill published in the GitHub repository umputun/cc-thingz (466 stars, last pushed 12d ago), licensed MIT. It adds 87 tokens to every session and 1,477 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-30.
Other skills, from other repositories
plugin
Manage Claude Code plugins — add marketplaces, install, update, remove, list. Use when installing plugins, checking status, or managing the registry.
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-land
Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LANDVERDICT. Use when asked to land PRs.
flow-next-spec-completion-review
Verify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.
flow-next-guide
Recommend the smallest sufficient flow-next workflow from the starting state. Stateless router. Use when unsure which command or stage applies next.
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).