Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Bitmia-ai/RedEyenpx agentmods add commands/bitmia-ai/redeye/brainstormWrote 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/bitmia-ai/redeye/brainstorm)<a href="https://agentmods.dev/commands/bitmia-ai/redeye/brainstorm"><img src="https://agentmods.dev/badge/commands/bitmia-ai/redeye/brainstorm/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/bitmia-ai/redeye/brainstorm"><img src="https://agentmods.dev/badge/commands/bitmia-ai/redeye/brainstorm.svg" alt="Reviewed on agentmods" width="80" 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.00010 | $0.00418 |
| Opus 5.5 | $0.00004 | $0.00167 |
| Sonnet 5.5 | $0.00002 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
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 1mo 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
If arguments provided, use them as the starting idea. Otherwise, ask: "What would you like to brainstorm?"
-
Invoke
superpowers:brainstormingto explore the idea with the user -
When the brainstorm produces a design/brief, save it to
docs/briefs/{date}-{slug}.md -
Read
.redeye/state.jsonto getcounters.next_task_id -
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 -
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}.mdThe script allocates the next
T<NNN>ID atomically, writes the canonical block, and bumpsstate.json.counters.next_task_id. Seetemplates/TASK_FORMAT.mdfor the parser contract. -
Increment
counters.next_task_idin.redeye/state.json -
Commit:
git add docs/briefs/ .redeye/tasks.md .redeye/state.json && git commit -m "redeye: brainstorm — {title}" -
Tell the user: "Added T{id}: {title} to task list with brief at docs/briefs/{filename}."
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.
- 1mo ago First seen · 33 lines · 10 tokens per session scan A 216b57135f80
brainstorm is a command published in the GitHub repository Bitmia-ai/RedEye (6 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 418 once invoked, about $0.0000 per session on Opus 5.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
poc
Before building on an unproven idea, get a timeboxed yes/no answer — start a hypothesis-driven POC that skips 80% of the production pipeline and forces ship/pivot/kill at expiry, then promote a shipped POC through the audits it skipped.
spec
Know the problem but not yet the product, the requirements or the design? Run it — you get, stage by stage, a discovery plan (/spec discover), a PRD (/spec prd) and a build spec: requirements.md + design.md + tasks.md (/spec or /spec build). Run before writing any code.
ownership
When you need to know who owns a path and who answers for it — the service ownership matrix (team, lead, on-call, SLA) auto-detected from git with CODEOWNERS generated, plus on-call rotations, shift handoffs and escalation paths.
rfc
RFC process for cross-team decisions. Create, track, and close RFCs. Accepted RFCs auto-create ADRs.
exception
Signed gate-exception registry — replace ad-hoc --admin / --no-verify bypasses with an auditable, signed, expiring record (who · why · gate · scope · expiry). Create / list / check exceptions.
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.