Borrowing it
Nothing to install: this file belongs to lxyer/multi-agent-collaboration-system. 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/lxyer/multi-agent-collaboration-system/main/.agents/skills/brainstorm/SKILL.mdgit 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/skills/lxyer/multi-agent-collaboration-system/brainstorm)<a href="https://agentmods.dev/skills/lxyer/multi-agent-collaboration-system/brainstorm"><img src="https://agentmods.dev/badge/skills/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.1 | $0.00072 | $0.02883 |
| Opus 5 | $0.00036 | $0.01442 |
| Sonnet 5 | $0.00014 | $0.00577 |
| Haiku 4.5 | $0.00007 | $0.00288 |
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 7d 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 — 493 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 $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.
- 7d ago First seen · 493 lines · 72 tokens per session scan A 2fc7fee5ce4d
brainstorm is a skill published in the GitHub repository lxyer/multi-agent-collaboration-system (1 stars, last pushed 4mo ago), licensed MIT. It adds 72 tokens to every session and 2,883 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-31.
Other skills, from other repositories
meta-cognition-parallel
An experimental tool for analysing a question or problem in parallel across three layers.
rust-learner
Use when asking about Rust versions or crate info. Keywords: latest version, what's new, changelog, Rust 1.x, Rust release, stable, nightly, crate info, crates.io, lib.rs, docs.rs, API documentation, crate features, dependencies, which crate, what version, Rust edition, edition 2021, edition 2024, cargo add, cargo…
rust-router
A routing skill for Rust development questions, including errors, design choices, comparisons, and coding tasks involving Rust tools and packages.
m07-concurrency
A guide to running work at the same time in Rust, either on threads or through async tasks. It covers shared data, channels, locks, atomics, futures, and common problems such as races and deadlocks.
rust-call-graph
A visualisation tool for Rust function call graphs, showing which functions call one another.
rust-daily
A reporting helper for Rust news, including daily, weekly, and monthly updates.