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 skills/matrixfounder/agentic-development/brainstormingnpx skills add MatrixFounder/Agentic-development --skill brainstorminggit clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentWhat 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.00030 | $0.01164 |
| Opus 5 | $0.00015 | $0.00582 |
| Sonnet 5 | $0.00006 | $0.00233 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
brainstorming 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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Universal Brainstorming Protocol
Purpose: Bridge the gap between user intent ("Make it pop") and technical specification ("CSS Box Shadow"). Core Rule: Do NOT write code until you have a confirmed design (except for Trivial tasks).
Phase 1: Assess & Understand
1. Complexity Assessment (MANDATORY) At the start, classify the task to determine your mode:
| Level | Criteria | Protocol | Reference |
|---|---|---|---|
| TRIVIAL | Clear requirements, standard pattern, single component (e.g., "Fix typo", "Add log"). | Fast Path: Skip deep research. Confirm plan in chat. Go. | examples/demo_trivial.md |
| MEDIUM | Standard task but open details (e.g., "Add button", "Refactor function"). | Standard: 1-2 clarifying questions, 2 options, brief confirmation. | examples/demo_medium.md |
| COMPLEX | High uncertainty, architectural impact, multiple components (e.g., "New System"). | Deep Dive: Research -> Mermaid -> Trade-offs -> Design Doc -> Sign-off. | examples/demo_complex.md |
2. Context Gathering (Tool Agnostic)
- Search: Use your environment's search capability (e.g.,
grep,search_code) to understand existing patterns.- Guardrail: IF NO SEARCH TOOLS EXIST, do NOT guess. Explicitly ask the user: "I cannot scan the repo. Could you share
package.jsonand relevant files?"
- Guardrail: IF NO SEARCH TOOLS EXIST, do NOT guess. Explicitly ask the user: "I cannot scan the repo. Could you share
- Reading: Preferentially read
task.md,README.md, or.cursorrulesto align with project standards.
Phase 2: Explore & Visualize (The "How")
1. Smart Questions
- Ask ONE critical question at a time.
- Template: "To match your existing patterns for [X], do you prefer [Option A] or [Option B]?"
2. Visual Thinking
- Constraint: For MEDIUM/COMPLEX tasks, you MUST visualize the flow.
- Primary: Mermaid (Flowcharts/Sequence) only if confident the user's UI supports it.
- Fallback: ASCII Art or Bullet Lists if the environment is restricted (e.g., standard terminal).
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 82 lines · 30 tokens per session scan A 474728fb2185
brainstorming is a skill published in the GitHub repository MatrixFounder/Agentic-development (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,164 once invoked, about $0.0002 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
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
extension-creator
Create, scaffold, customize, validate, and locally test Qwen Code extensions. Use when the user wants a new Qwen Code extension, needs help choosing an extension template, wants to add QWEN.md context, commands, skills, agents, MCP servers, settings, hooks, channels, or LSP servers, or asks how to link and test an…
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
pr-feedback
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.
argent-native-profiler
Native profiling for CPU hotspots, UI hangs, memory issues. iOS via xctrace; Android via Perfetto. Use when diagnosing native-level performance issues.
argent-tv-interact
Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…