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/lxyer/multi-agent-collaboration-system/brainstormgit clone --depth 1 https://github.com/lxyer/multi-agent-collaboration-systemWrote 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/lxyer/multi-agent-collaboration-system/brainstorm)<a href="https://agentmods.dev/commands/lxyer/multi-agent-collaboration-system/brainstorm"><img src="https://agentmods.dev/badge/commands/lxyer/multi-agent-collaboration-system/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.00000 | $0.02814 |
| Opus 5 | $0.00000 | $0.01407 |
| Sonnet 5 | $0.00000 | $0.00563 |
| Haiku 4.5 | $0.00000 | $0.00281 |
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 5d 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
100% identical to brainstorm — 0 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 — 488 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm - Requirements Discovery (AI Coding Enhanced)
Guide AI through collaborative requirements discovery before implementation, optimized for AI coding workflows:
- Task-first (capture ideas immediately)
- Action-before-asking (reduce low-value questions)
- Research-first for technical choices (avoid asking users to invent options)
- Diverge → Converge (expand thinking, then lock MVP)
When to Use
Triggered from /trellis:start when the user describes a development task, especially when:
- requirements are unclear or evolving
- there are multiple valid implementation paths
- trade-offs matter (UX, reliability, maintainability, cost, performance)
- the user might not know the best options up front
Core Principles (Non-negotiable)
-
Task-first (capture early) Always ensure a task exists at the start so the user's ideas are recorded immediately.
-
Action before asking If you can derive the answer from repo code, docs, configs, conventions, or quick research — do that first.
-
One question per message Never overwhelm the user with a list of questions. Ask one, update PRD, repeat.
-
Prefer concrete options For preference/decision questions, present 2–3 feasible, specific approaches with trade-offs.
-
Research-first for technical choices If the decision depends on industry conventions / similar tools / established patterns, do research first, then propose options.
-
Diverge → Converge After initial understanding, proactively consider future evolution, related scenarios, and failure/edge cases — then converge to an MVP with explicit out-of-scope.
-
No meta questions Do not ask "should I search?" or "can you paste the code so I can continue?" If you need information: search/inspect. If blocked: ask the minimal blocking question.
Step 0: Ensure Task Exists (ALWAYS)
Before any Q&A, ensure a task exists. If none exists, create one immediately.
- Use a temporary working title derived from the user's message.
- It's OK if the title is imperfect — refine later in PRD.
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.
- 5d ago First seen · 488 lines · 0 tokens per session scan A 7c7731eda092
brainstorm is a command published in the GitHub repository lxyer/multi-agent-collaboration-system (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,814 tokens. A static security scan graded it A with 0 findings. It is 100% identical to brainstorm, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
ai-daily
Generate AI daily/weekly news report from Reddit communities.
rust-daily
Generate Rust daily/weekly/monthly news report.
create-llms-from-source
Generate llms.txt from local Rust source code.
create-llms-for-skills
Generate comprehensive llms.txt from URLs using agent-browser.
create-skills-via-llms
Create high-quality Rust crate skills from llms.txt.
audit
Heavy-weight security and safety audit using os-checker tools.