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/mrvladd-d/memobank/brainstormgit clone --depth 1 https://github.com/mrvladd-d/memobankWrote 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/mrvladd-d/memobank/brainstorm)<a href="https://agentmods.dev/commands/mrvladd-d/memobank/brainstorm"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/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 | $0.00017 | $0.00757 |
| Opus 5 | $0.00009 | $0.00378 |
| Sonnet 5 | $0.00003 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00076 |
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 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/brainstorm - Facilitated ideation
The AI is a facilitator and coach. The user is the source of product intent, priorities, and decisions. Raw ideas do not become requirements directly.
0) Scope
Use /brainstorm when the idea is raw, the problem space is unclear, or there are too many possible directions.
Do not create:
- PRD
- Product Brief, unless the user separately invokes
/brief - task records
- implementation plans
- research reports
- PRFAQ
.memory-bank/analysis/assumptions.md- command aliases
No research mode. If research is needed, record it as an open question or risk.
1) Prepare artifacts
Create if missing:
.memory-bank/analysis/index.md.memory-bank/analysis/brainstorming/
When creating .memory-bank/analysis/index.md, include:
---
description: Analysis artifact index.
status: active
---
Create a new report:
.memory-bank/analysis/brainstorming/BR-001.md
If BR-001.md exists, use the next available ID: BR-002.md, BR-003.md, and so on.
Update .memory-bank/analysis/index.md with the latest report link and:
Recommended next step: /brief
2) Facilitate, do not invent
Start by asking for or confirming:
- problem space
- target users
- user goals
- constraints
- what the user already believes or wants to avoid
Use lightweight ideation only as needed:
- alternative user journeys
- pain points
- solution directions
- constraints-first thinking
- risk-first thinking
- MVP slicing
Default target is 20-40 useful ideas or directions only when expansion is useful. If the user already has a clear direction, keep the session short.
3) Report structure
Write the report with these sections:
---
description: Brainstorming report BR-<NNN>.
status: active
type: brainstorming-report
id: BR-<NNN>
---
# Brainstorming Report - BR-<NNN>
## Status
- Date: YYYY-MM-DD
- Facilitator: AI
- Source of product intent: user
- Recommended next step: /brief
## Problem Space
## Goals
## Constraints
## Techniques Used
## Raw Ideas
## Clusters / Themes
## Selected Directions
## Rejected Directions
## Assumptions
## Open Questions
## Recommended Next Step
/brief
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 · 131 lines · 17 tokens per session scan A 172eeeecc623
brainstorm is a command published in the GitHub repository mrvladd-d/memobank (55 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 757 once invoked, about $0.0001 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.