brainstorm

brainstorm is a command for Claude Code from revaya-ai/revaya-aios-workspace-template. It costs 0 tokens per session (1,749 once invoked), scanned A, original, MIT.

A guided command for examining your workspace and finding useful things to build, automate, or organise. It produces a written brainstorming document rather than making changes.

In plain words
What is it for?
Use it to review current work, spot automation opportunities, and prepare an idea for a later exploration or implementation step.
Why use it?
It helps turn scattered tasks and repetitive manual work into a short list of possible improvements, then identify which idea is most worth pursuing.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md; mentions Claude Code.

Good fit Use it to review current work, spot automation opportunities, and prepare an idea for a later exploration or implementation step.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/revaya-ai/revaya-aios-workspace-template/brainstorm
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.

Clone the repo
git clone --depth 1 https://github.com/revaya-ai/revaya-aios-workspace-template

Made for: Claude Code.

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

agentmods badge for brainstorm

README.md
[![agentmods](https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/brainstorm/github.svg)](https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/brainstorm)
Your own site
<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/brainstorm"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/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.

agentmods 80×15 button for brainstorm

Your own site · 80×15
<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/brainstorm"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/brainstorm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,749 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.01749
Opus 5 $0.00000 $0.00874
Sonnet 5 $0.00000 $0.00350
Haiku 4.5 $0.00000 $0.00175

Measured 11d ago against content hash a65006df9320, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 11d 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.

.claude/commands/brainstorm.md · 190 lines

How it starts

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

Brainstorm

Look at your workspace — your tasks, your workflows, your daily work — and brainstorm what to build, automate, or systematize next.

Variables

topic: $ARGUMENTS (optional — a specific area to focus on, or leave blank to scan everything)


Instructions

You are running a brainstorm session. Your job is to help the user figure out what to build next by looking at their actual work — tasks, manual processes, repeated actions — and identifying the best opportunities to automate or systematize.

This is NOT about building anything yet. This is about finding the right thing to build. The output feeds into /explore (to shape an idea) or /implement (if it's obvious what to do).

Tone: Conversational and encouraging. The user may not know what's possible — your job is to show them. Get excited about the opportunities you find.

Output: A brainstorm doc saved to plans/brainstorm-YYYY-MM-DD-{topic}.md


Stage 1: SCAN — Understand Their World

Goal: Map out what the user is currently doing, what's manual, and where the opportunities are.

Actions:

  1. Read the workspace to understand the user's setup:

    • CLAUDE.md — what systems exist, what commands are available, what's already automated
    • Any task audit, task list, or project tracking files in the workspace (search for files containing tasks, todos, audits, or project lists)
    • Any context files about their business, role, or current priorities
    • GTD files if ProductivityOS is installed (gtd/projects.md, gtd/next-actions.md)
  2. If a specific topic was provided, focus on that area. If not, scan broadly.

  3. Build a picture of:

    • What's already automated — systems, commands, cron jobs, scripts they have
    • What's still manual — tasks, processes, workflows they do by hand
    • What data they have — databases, files, APIs connected
    • What tools they use — services, platforms, integrations
  4. Present a summary:

    Here's what I see in your workspace:
    
    Already automated:
    - {system 1} — {what it does}
    - {system 2} — {what it does}
    
    Still manual (opportunities):
    - {task/process 1} — {how often, how painful}
    - {task/process 2} — {how often, how painful}
    - {task/process 3} — {how often, how painful}
    
    Data available:
    - {what data exists that could power new systems}
    

Read the full file on GitHub · 190 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. 11d ago First seen · 190 lines · 0 tokens per session scan A a65006df9320

Subscribe to this mod's changes

brainstorm is a command published in the GitHub repository revaya-ai/revaya-aios-workspace-template (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,749 tokens. 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.