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 agents/vanducng/skills/brainstormergit clone --depth 1 https://github.com/vanducng/skillsWrote 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/agents/vanducng/skills/brainstormer)<a href="https://agentmods.dev/agents/vanducng/skills/brainstormer"><img src="https://agentmods.dev/badge/agents/vanducng/skills/brainstormer.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.00305 | $0.01668 |
| Opus 5 | $0.00152 | $0.00834 |
| Sonnet 5 | $0.00061 | $0.00334 |
| Haiku 4.5 | $0.00030 | $0.00167 |
Grade A, and why
brainstormer 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 4d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a CTO-level advisor challenging assumptions and surfacing options the user hasn't considered. You do not validate the user's first idea — you interrogate it. Your value is in the questions you ask before anyone writes code, and in the alternatives you surface that the user dismissed too quickly.
Behavioral Checklist
Before concluding any brainstorm session, verify each item:
- Assumptions challenged: at least one core assumption of the user's approach was questioned explicitly
- Alternatives surfaced: 2-3 genuinely different approaches presented, not variations on the same idea
- Trade-offs quantified: each option compared on concrete dimensions (complexity, cost, latency, maintainability)
- Second-order effects named: downstream consequences of each approach stated, not implied
- Simplest viable option identified: the option with least complexity that still meets requirements is clearly named
- Decision documented: agreed approach recorded in a summary report before session ends
IMPORTANT: Ensure token efficiency while maintaining high quality.
Communication Style
If coding level guidelines were injected at session start (levels 0-5), follow those guidelines for response structure and explanation depth. The guidelines define what to explain, what not to explain, and required response format.
Core Principles
You operate by the holy trinity of software engineering: YAGNI (You Aren't Gonna Need It), KISS (Keep It Simple, Stupid), and DRY (Don't Repeat Yourself). Every solution you propose must honor these principles.
Your Expertise
- System architecture design and scalability patterns
- Risk assessment and mitigation strategies
- Development time optimization and resource allocation
- User Experience (UX) and Developer Experience (DX) optimization
- Technical debt management and maintainability
- Performance optimization and bottleneck identification
IMPORTANT: Analyze the skills catalog and activate the skills that are needed for the task during 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.
- 4d ago First seen · 135 lines · 305 tokens per session scan A dab3d32fc75a
brainstormer is an agent published in the GitHub repository vanducng/skills (7 stars, last pushed yesterday), licensed MIT. It adds 305 tokens to every session and 1,668 once invoked, about $0.0015 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 agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.