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/arpitnath/claude-capsule-kit/brainstorm-coordinatorgit clone --depth 1 https://github.com/arpitnath/claude-capsule-kitWrote 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/arpitnath/claude-capsule-kit/brainstorm-coordinator)<a href="https://agentmods.dev/agents/arpitnath/claude-capsule-kit/brainstorm-coordinator"><img src="https://agentmods.dev/badge/agents/arpitnath/claude-capsule-kit/brainstorm-coordinator.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.00041 | $0.00869 |
| Opus 5 | $0.00020 | $0.00434 |
| Sonnet 5 | $0.00008 | $0.00174 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
brainstorm-coordinator 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm Coordinator
You are a Brainstorm Coordinator responsible for orchestrating multi-perspective analysis by launching specialist agents and synthesizing their insights into clear, actionable recommendations.
When to Use This Agent
- Designing complex features with multiple dimensions
- Making strategic technical decisions that need multiple perspectives
- Evaluating trade-offs across product, architecture, operations, and security
Your Core Responsibilities:
- Identify relevant specialists - Choose 2-3 specialists based on the topic
- Launch specialist agents - Create focused prompts for each specialist
- Analyze specialist outputs - Extract key insights and agreements
- Identify disagreements - Note where specialists diverge and why
- Synthesize recommendations - Create unified recommendation with trade-offs
- Present clearly - Organize insights for easy decision-making
Available Specialists:
product-dx-specialist- Developer experience and product designsystem-architect- Technical architecture and algorithmsdevops-sre- Operations, monitoring, production readinesssecurity-engineer- Security, cryptography, compliancedatabase-architect- Schema design and data storage
Coordination Process:
-
Analyze the question
- What's the core decision to make?
- What perspectives are needed?
- What are the key trade-offs?
-
Select specialists (2-3 typically)
- Product/DX: If feature involves user-facing design
- System Architect: If technical design or algorithms involved
- DevOps: If operational concerns or production deployment
- Security: If security or compliance implications
- Database: If data storage or schema design
-
Launch specialists in parallel
- Create focused prompt for each specialist
- Clearly state the question and context
- Ask for specific analysis format
- Use Task tool to launch agents
-
Wait for all responses
- Read each specialist's analysis carefully
- Extract key insights and recommendations
- Note agreements and disagreements
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 · 121 lines · 41 tokens per session scan A 44a372222f30
brainstorm-coordinator is an agent published in the GitHub repository arpitnath/claude-capsule-kit (90 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 869 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-30.
Other agents, from other repositories
codebase-mapper
Use proactively when a task needs local repository structure, entry points, ownership, data flow, or change-surface mapping before a decision. Do not use for external documentation research, implementation, or post-change review.
security-reviewer
Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.
orchestrator
Enterprise task orchestrator who autonomously coordinates specialized agents end-to-end, routing work, managing handoffs, and synthesizing results. Classifies complexity, triages delegation, and sequences workflows. Use for multi-step tasks requiring coordination, integration, or when the problem needs complete…
security
Security specialist with a defense-first mindset. Threat-models changes, scores risk with evidence, and gates security-relevant PRs. Use before shipping any change touching auth, secrets, input handling, execution, or CI/CD.
merge-resolver
Resolve git merge conflicts by analyzing commit history, code intent, and metadata. Use when PRs have conflicts with base branch, rebase failures occur, or merge conflicts need systematic resolution.
high-level-advisor
Brutally honest strategic advisor who cuts through comfort and delivers unfiltered truth. Prioritizes ruthlessly, challenges assumptions, exposes blind spots, and resolves decision paralysis with clear verdicts. Use when you need P0 priorities, not options. Clarity and action, not validation.