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 commands/thierryn/fire-flow/fire-brainstormgit clone --depth 1 https://github.com/ThierryN/fire-flowWrote 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/thierryn/fire-flow/fire-brainstorm)<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-brainstorm"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-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.00007 | $0.02343 |
| Opus 5 | $0.00003 | $0.01171 |
| Sonnet 5 | $0.00001 | $0.00469 |
| Haiku 4.5 | $0.00001 | $0.00234 |
Grade A, and why
fire-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 — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-brainstorm
Explore ideas thoroughly before committing to implementation
Purpose
A dedicated ideation phase inspired by superpowers:brainstorming. Forces divergent thinking, explores alternatives, and documents decisions BEFORE writing code. Prevents premature implementation and ensures requirements are understood.
Arguments
arguments:
topic:
required: true
type: string
description: "What to brainstorm - feature, architecture, problem, etc."
examples:
- "/fire-brainstorm 'user authentication system'"
- "/fire-brainstorm 'how to handle file uploads'"
- "/fire-brainstorm 'database schema for orders'"
optional_flags:
--constraints: "Comma-separated constraints to consider"
--time-box: "Limit brainstorm duration (e.g., '15min')"
--perspectives: "Number of alternative approaches to explore (default: 3)"
--output: "Save brainstorm to file (default: .planning/brainstorms/)"
--no-questions: "Skip clarifying questions, use assumptions"
Process
Step 1: Initialize Brainstorm Session
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
DOMINION FLOW ► BRAINSTORM SESSION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Topic: {topic}
Mode: Exploration (no code yet)
Step 2: Clarifying Questions (Unless --no-questions)
MANDATORY: Understand before exploring.
## Clarifying Questions
Before exploring solutions, I need to understand the problem space.
### Scope Questions
1. What is the primary user/use case for this?
2. What systems/components does this interact with?
3. Are there existing patterns in the codebase to follow?
### Constraint Questions
4. What are the non-negotiables (must-haves)?
5. What are known limitations (tech stack, budget, time)?
6. Are there security/compliance requirements?
### Context Questions
7. Has this been attempted before? What happened?
8. What does "success" look like?
9. Who are the stakeholders?
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 · 414 lines · 7 tokens per session scan A 8493c4e34b32
fire-brainstorm is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 21d ago), licensed MIT. It adds 7 tokens to every session and 2,343 once invoked, about $0.0000 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.