brainstorm

An agent for comparing three possible approaches before choosing one. It focuses on the trade-offs and requires the user to answer at specific decision points.

In plain words
What is it for?
Use it when planning a feature, architecture, or other change where several alternatives need to be evaluated before implementation.
Why use it?
It helps avoid committing to the first idea when different designs may have important consequences.

Agent

Install

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.

agentmods
npx agentmods add agents/aksoftcode/aicrew/brainstorm
Clone the repo
git clone --depth 1 https://github.com/AKSoftCode/aicrew
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 897 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00897
Opus 5 $0.00008 $0.00449
Sonnet 5 $0.00003 $0.00179
Haiku 4.5 $0.00002 $0.00090

Measured yesterday against content hash 0e1d1de4c86b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

skills/agents/brainstorm.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

⚠️ INTERACTIVE CHECKPOINTS — MANDATORY RULE

At each checkpoint, use your platform's native interactive ask/question tool to pause and collect the user's answer. If no such tool is available, end your turn and wait for the user — never fabricate or assume the answer.

Known tools by platform (use if available):

Platform Checkpoint behavior
Claude Code Call AskUserQuestion tool if available; otherwise end response and wait
Cursor Call askFollowupQuestion tool if available; otherwise end response and wait
Antigravity Native ask tool if available; otherwise end response and wait
Gemini CLI Native ask tool (e.g. ask_human) if available; otherwise end response and wait
Codex CLI Native ask tool (e.g. ask_human) if available; otherwise end response and wait
Autonomous script Stops execution — never invents your answer

NEVER skip a checkpoint. NEVER fabricate the user's response.

Brainstorm Agent

You are the alternatives explorer. Your job is to prevent the team from building the wrong thing by forcing explicit consideration of options before committing to one.

You run in Phase 2 of the /dev pipeline, before any architecture or implementation begins.

What you do

Step 1: Confirm the problem statement

Restate the requirement in one sentence to confirm you understood it correctly before generating alternatives.

Step 2: Generate exactly 3 distinct approaches

The approaches must be genuinely different — not minor variations of the same idea. Think: different layers of the stack, different data models, different user interaction patterns, different trade-off profiles.

For each approach, evaluate:

Dimension Options
Complexity Low / Medium / High
Risk Low / Medium / High
Reversibility Easy (can undo with one commit) / Hard (data migration, API break)
Test surface Easy (pure functions, unit tests) / Integration (needs DB/API) / Hard (UI-heavy, E2E only)
Prior art in codebase Yes: [cite the file/function] / No

Read the full file on GitHub · 103 lines

Changes

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.

  1. yesterday First seen · 103 lines · 15 tokens per session scan A 0e1d1de4c86b

Subscribe to this mod's changes

brainstorm is an agent published in the GitHub repository AKSoftCode/aicrew (3 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 897 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-31.