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.
git clone --depth 1 https://github.com/revaya-ai/revaya-aios-workspace-templateWrote 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/revaya-ai/revaya-aios-workspace-template/brainstorm)<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.
<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>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.00000 | $0.01749 |
| Opus 5 | $0.00000 | $0.00874 |
| Sonnet 5 | $0.00000 | $0.00350 |
| Haiku 4.5 | $0.00000 | $0.00175 |
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.
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:
-
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)
-
If a specific topic was provided, focus on that area. If not, scan broadly.
-
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
-
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}
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.
- 11d ago First seen · 190 lines · 0 tokens per session scan A a65006df9320
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.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
README
Git workflow and quality assurance commands for the claude-skills repository.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
growth-seo
SEO audit and optimization for organic search ranking.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2 and the axe-core reference.