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/rasputinkaiser/self-improvement-plugin/brainstormgit clone --depth 1 https://github.com/RasputinKaiser/Self-Improvement-PluginWhat 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.00039 | $0.00442 |
| Opus 5 | $0.00019 | $0.00221 |
| Sonnet 5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
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 2d 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.
What it actually says
The JSON response also includes bounded idea_cards. Each card has a stable
ID, source signal, leverage/effort, and a plan card using the
Scout → Judge → Worker → verify sequence. Cards are suggestions only:
brainstorm does not create tasks, write code, or claim that a suggested change
has been verified.
Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/brainstorm.py --json to survey current capabilities and identify gaps. The response keeps the legacy gaps array and adds 3-5 ranked idea_cards, each with a stable ID, source signal, plan, effort estimate, and leverage score.
Read the result. Then dispatch the escalate agent to draft a full build plan for the highest-leverage gap (the top entry). Give the escalate agent:
- The gap name and description
- The current capability map (from
references/capability_map.mdin this plugin) - Instruction to produce: a phased plan with concrete file paths, new types/modules, UX patterns to borrow from Codex App / Claude Code, test strategy, and risk/rollback notes
- Constraint: do NOT write any code — produce the plan only. The user will review and decide whether to implement.
Present the user with:
- Ranked gap list (3-5 items with effort + leverage scores)
- The escalated plan for the top gap (full architecture, phased build order)
Append a one-line summary to ${SIPS_HOME:-$HOME/.codex/sips}/improvements.md under ## /brainstorm sweep — <ts> noting what the top gap was and whether the escalate agent produced a plan.
Do not edit ${CLAUDE_PLUGIN_ROOT}/scripts/* or the SIPS plugin source beyond the journal append. If the escalate agent suggests code changes, surface them as proposals only - the user explicitly reviews before any implementation.
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.
- 2d ago First seen · 29 lines · 39 tokens per session scan A 2f05abdf5fd6
brainstorm is a command published in the GitHub repository RasputinKaiser/Self-Improvement-Plugin (6 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 442 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-31.
Other commands, from other repositories
feature
Orchestrate a complete feature through discovery, spec, implementation, and review.
spec
Turn an objective into a spec and implementable tasks.
research
Research a technical or product question.
fic-create-plan
Act as a Senior XP Developer creating detailed implementation plans through interactive, iterative collaboration.
reqforge-greenkeeper
Diagnose and fix ReqForge repository release gate failures.
evolution-engine
Scan feedback and generate evolution proposals for rule/skill upgrades.