brainstorm

A command that turns a feature idea into a short design brief and a tracked development task. It uses a brainstorming step, saves the brief, and files the task through the project's task-creation script.

In plain words
What is it for?
Use it to explore a feature idea, save a dated brief under docs/briefs, and create a prioritized CEO request in the project's task system.
Why use it?
It keeps early product thinking and the resulting work item connected, with the next task number assigned from the project's state.

Command

Part of the redeye plugin — 10 commands, 13 agents, 1 hook shipped together

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 commands/bitmia-ai/redeye/brainstorm
Clone the repo
git clone --depth 1 https://github.com/Bitmia-ai/RedEye

Or install redeye, the plugin that ships this one along with the rest of its 10 commands, 13 agents, 1 hook.

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 418 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.00010 $0.00418
Opus 5 $0.00005 $0.00209
Sonnet 5 $0.00002 $0.00084
Haiku 4.5 $0.00001 $0.00042

Measured 3d ago against content hash 216b57135f80, 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 3d 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.

commands/brainstorm.md · 33 lines

What it actually says

If arguments provided, use them as the starting idea. Otherwise, ask: "What would you like to brainstorm?"

  1. Invoke superpowers:brainstorming to explore the idea with the user

  2. When the brainstorm produces a design/brief, save it to docs/briefs/{date}-{slug}.md

  3. Read .redeye/state.json to get counters.next_task_id

  4. Write a description body to a temp file (Markdown OK — sub-headers as **bold**, NOT as - **Xxx:** bullets):

    cat > /tmp/redeye-brainstorm-{id}.md <<'EOF'
    **Brief:** [docs/briefs/{filename}](docs/briefs/{filename})
    
    {one-paragraph summary of the brainstorm outcome — what the feature is and why it matters}
    EOF
    
  5. File the CEO Request via scripts/create-task.sh (the ONLY supported path for creating tasks):

    bash scripts/create-task.sh \
      --section ceo \
      --title "{title from brainstorm}" \
      --type feature \
      --priority P2 \
      --description-file /tmp/redeye-brainstorm-{id}.md
    

    The script allocates the next T<NNN> ID atomically, writes the canonical block, and bumps state.json.counters.next_task_id. See templates/TASK_FORMAT.md for the parser contract.

  6. Increment counters.next_task_id in .redeye/state.json

  7. Commit: git add docs/briefs/ .redeye/tasks.md .redeye/state.json && git commit -m "redeye: brainstorm — {title}"

  8. Tell the user: "Added T{id}: {title} to task list with brief at docs/briefs/{filename}."

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. 3d ago First seen · 33 lines · 10 tokens per session scan A 216b57135f80

Subscribe to this mod's changes

brainstorm is a command published in the GitHub repository Bitmia-ai/RedEye (6 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 418 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.