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 commands/mrgoonie/human-mcp/brainstormgit clone --depth 1 https://github.com/mrgoonie/human-mcpWrote 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/commands/mrgoonie/human-mcp/brainstorm)<a href="https://agentmods.dev/commands/mrgoonie/human-mcp/brainstorm"><img src="https://agentmods.dev/badge/commands/mrgoonie/human-mcp/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.00004 | $0.00767 |
| Opus 5 | $0.00002 | $0.00383 |
| Sonnet 5 | $0.00001 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00077 |
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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- brainstorm — 92% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 68 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 and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
Answer this question:
$ARGUMENTS
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
Your Approach
-
Question Everything: Ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
-
Brutal Honesty: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
-
Explore Alternatives: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior.
-
Challenge Assumptions: Question the user's initial approach. Often the best solution is different from what was originally envisioned.
-
Consider All Stakeholders: Evaluate impact on end users, developers, operations team, and business objectives.
Collaboration Tools
- Consult the
planneragent to research industry best practices and find proven solutions - Engage the
docs-manageragent to understand existing project implementation and constraints - Use
Search Googletool fromsearchapiMCP server to find efficient approaches and learn from others' experiences - Use
context7MCP tools to read latest documentation of external plugins/packages - Leverage
eyes_analyzefrom Human MCP to analyze visual materials and mockups - Query
psqlcommand to understand current database structure and existing data - Employ
brainMCP tools for complex problem-solving that requires structured analysis
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.
- 6d ago First seen · 68 lines · 4 tokens per session scan A 7160ef8ad408
brainstorm is a command published in the GitHub repository mrgoonie/human-mcp (294 stars, last pushed 5mo ago), licensed MIT. It adds 4 tokens to every session and 767 once invoked, about $0.0000 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 commands, from other repositories
report
Generate a project analytics report covering code quality, velocity, and health metrics.
explain
Explain a code file, function, or concept in clear, structured language.
debug-pod
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.
env-setup
Set up environment configuration files from templates with validation.
document-all
Auto-document the entire codebase by generating module-level docs, function signatures, and API references.
complete
Complete a partially implemented feature by filling gaps and ensuring production readiness.