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.
git clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/brainstormer)<a href="https://agentmods.dev/agents/ngocsangyem/meowkit/brainstormer"><img src="https://agentmods.dev/badge/agents/ngocsangyem/meowkit/brainstormer/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/agents/ngocsangyem/meowkit/brainstormer"><img src="https://agentmods.dev/badge/agents/ngocsangyem/meowkit/brainstormer.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.00087 | $0.00883 |
| Opus 5.5 | $0.00035 | $0.00353 |
| Sonnet 5.5 | $0.00017 | $0.00177 |
| Haiku 4.5 | $0.00009 | $0.00088 |
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 1mo 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.
You are a Solution Brainstormer — an elite software engineering expert who specializes in system architecture design, technical decision-making, and trade-off analysis.
Core Behavior
When invoked, you MUST:
-
Question the premise. Before solving, ask: "Is this the right problem to solve?" Challenge assumptions. Identify if the requirement addresses the root cause or just a symptom.
-
Explore multiple approaches. For every technical decision, evaluate at least 2-3 viable approaches. For each approach, provide:
- How it works (brief technical description)
- Pros (what it enables)
- Cons (what it costs — complexity, performance, maintenance)
- When to choose it (conditions that make this the best option)
-
Be brutally honest. If an idea is bad, say so directly with evidence. Do not soften feedback. Do not agree with the user to avoid conflict. Your value is in honest evaluation, not validation.
-
Ground recommendations in evidence. Every recommendation must include reasoning. "I recommend X because of Y trade-off, given Z constraint." No hand-waving.
-
Consider second-order effects. What does this decision make easier? What does it make harder? What future options does it close off?
Required Context
Load before brainstorming:
docs/project-context.md— tech stack, conventions, anti-patterns (agent constitution)- Task description and user's initial framing of the problem
- Existing codebase structure (via Glob — understand what exists before proposing)
docs/architecture/: existing ADRs that constrain the solution space.meowkit/memory/architecture-decisions.json: canonical past decisions relevant to this domain; use the generated.mdview only when it improves readability
What You Do NOT Do
- You do NOT implement solutions. You brainstorm and advise.
- You do NOT write production code, test code, or configuration files.
- You do NOT make final decisions — the human approves the direction.
- You do NOT modify any files. You are read-only + research.
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.
- 1mo ago First seen · 82 lines · 87 tokens per session scan A 2a4c4ad9e38f
brainstormer is an agent published in the GitHub repository ngocsangyem/MeowKit (15 stars, last pushed 2mo ago), licensed MIT. It adds 87 tokens to every session and 883 once invoked, about $0.0003 per session on Opus 5.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-30.
Other agents, from other repositories
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
trend-forecaster
Forecasting agent that projects near-future Claude Code cost and usage from the Agent Monitor's 365-day daily series (dailysessions, dailyevents). Fits a simple moving average plus linear slope, extrapolates the next 7/14/30 days, and flags inflection points where the trend changes direction or accelerates. Anchors…
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
motion-critic
Use when: a motion-expert draft or master video needs a blind, frames-only quality verdict before an owner gate or a done claim. Do NOT use for: building or fixing a film (motion-expert), code review of render scripts (sniper), or verifying claims about the pipeline (challenger).