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.
git clone --depth 1 https://github.com/rhuss/cc-spexWrote 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/commands/rhuss/cc-spex/speckit.spex.brainstorm)<a href="https://agentmods.dev/commands/rhuss/cc-spex/speckit.spex.brainstorm"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex.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.00017 | $0.05162 |
| Opus 5 | $0.00009 | $0.02581 |
| Sonnet 5 | $0.00003 | $0.01032 |
| Haiku 4.5 | $0.00002 | $0.00516 |
Grade A, and why
speckit.spex.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 8d 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 — 520 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Ideas Into Specifications
Help turn rough ideas into clear, agreed-upon feature descriptions through natural collaborative dialogue. The output is a brainstorm document capturing the problem, approaches considered, and the decision, ready for formal specification.
Key Principle: Brainstorming explores WHAT to build and WHY. The formal spec (via /speckit-specify) and implementation planning come after.
Idea Inbox: On startup, check brainstorm/idea-inbox.md for accumulated review ideas and offer them as brainstorm seeds (see step 3). After creating a brainstorm document from inbox items, remove consumed entries (see step 8). When invoked after a review discussion that contained deferred-idea signals ("out of scope", "worth considering later", "design tension", "follow-up", "for a future PR"), also mention that ideas can be added to the inbox manually.
spex extension commands use the speckit-spex-* prefix (e.g., /speckit-spex-brainstorm).
speckit core commands use the speckit- prefix (e.g., /speckit-specify, /speckit-plan).
Commands like /spex:specify, /spex:plan, /spex:implement, /spex:tasks DO NOT EXIST.
Checklist
You MUST create a task for each of these items and complete them in order:
- Initialize spec-kit - ensure specify CLI and project are set up
- Explore project context - check files, specs, constitution, recent commits
- Check idea inbox - check
brainstorm/idea-inbox.mdfor accumulated ideas from reviews, offer as brainstorm seeds - Check for related brainstorms - scan
brainstorm/for existing docs on similar topics, offer to update or create new - Ask clarifying questions - one at a time, understand purpose/constraints/success criteria
- Propose 2-3 approaches - with trade-offs and your recommendation
- Reach agreement - confirm the chosen approach and scope with the user
- Write brainstorm document - persist session summary to
brainstorm/NN-topic-slug.md, optionally create GitHub/GitLab issue. If seeded from inbox items, remove consumed entries frombrainstorm/idea-inbox.md - Update overview - create or refresh
brainstorm/00-overview.mdwith index, open threads, parked ideas - Transition - offer next steps
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.
- 8d ago First seen · 520 lines · 17 tokens per session scan A 73348f4a6c08
speckit.spex.brainstorm is a command published in the GitHub repository rhuss/cc-spex (115 stars, last pushed 20d ago), licensed Apache-2.0. It adds 17 tokens to every session and 5,162 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.