Borrowing it
Nothing to install: this file belongs to hollandkevint/thinkhaven. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hollandkevint/thinkhaven/main/.claude/commands/BMad/tasks/facilitate-brainstorming-session.mdgit clone --depth 1 https://github.com/hollandkevint/thinkhavenWrote 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/hollandkevint/thinkhaven/facilitate-brainstorming-session)<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/facilitate-brainstorming-session"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/facilitate-brainstorming-session/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/commands/hollandkevint/thinkhaven/facilitate-brainstorming-session"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/facilitate-brainstorming-session.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.00000 | $0.01035 |
| Opus 5 | $0.00000 | $0.00517 |
| Sonnet 5 | $0.00000 | $0.00207 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
facilitate-brainstorming-session 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 10d 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.
This is a copy
92% identical to facilitate-brainstorming-session — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/facilitate-brainstorming-session Task
When this command is used, execute the following task:
docOutputLocation: docs/brainstorming-session-results.md template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
Facilitate Brainstorming Session Task
Facilitate interactive brainstorming sessions with users. Be creative and adaptive in applying techniques.
Process
Step 1: Session Setup
Ask 4 context questions (don't preview what happens next):
- What are we brainstorming about?
- Any constraints or parameters?
- Goal: broad exploration or focused ideation?
- Do you want a structured document output to reference later? (Default Yes)
Step 2: Present Approach Options
After getting answers to Step 1, present 4 approach options (numbered):
- User selects specific techniques
- Analyst recommends techniques based on context
- Random technique selection for creative variety
- Progressive technique flow (start broad, narrow down)
Step 3: Execute Techniques Interactively
KEY PRINCIPLES:
- FACILITATOR ROLE: Guide user to generate their own ideas through questions, prompts, and examples
- CONTINUOUS ENGAGEMENT: Keep user engaged with chosen technique until they want to switch or are satisfied
- CAPTURE OUTPUT: If (default) document output requested, capture all ideas generated in each technique section to the document from the beginning.
Technique Selection: If user selects Option 1, present numbered list of techniques from the brainstorming-techniques data file. User can select by number..
Technique Execution:
- Apply selected technique according to data file description
- Keep engaging with technique until user indicates they want to:
- Choose a different technique
- Apply current ideas to a new technique
- Move to convergent phase
- End session
Output Capture (if requested): For each technique used, capture:
- Technique name and duration
- Key ideas generated by user
- Insights and patterns identified
- User's reflections on the process
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.
- 10d ago First seen · 143 lines · 0 tokens per session scan A cd364a4e9329
facilitate-brainstorming-session is a command published in the GitHub repository hollandkevint/thinkhaven (5 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,035 tokens. A static security scan graded it A with 0 findings. It is 92% identical to facilitate-brainstorming-session, differing in 6 lines, and is treated as a copy.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.