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.
npx agentmods add commands/aksoftcode/aicrew/brainstormgit clone --depth 1 https://github.com/AKSoftCode/aicrewWhat 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 | $0.00012 | $0.00325 |
| Opus 5 | $0.00006 | $0.00162 |
| Sonnet 5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
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.
What it actually says
Default output: caveman/lean — terse by default.
/normalor/lean offfor verbose.
/brainstorm
Generate 3 materially different approaches with trade-offs before committing to implementation.
Equivalent actions
| Method | Command |
|---|---|
| CLI | N/A (design tool, not CLI) |
| Codex skill | brainstorm |
| This slash command | /brainstorm [topic] |
When to use
- Before implementing a non-trivial feature
- When multiple valid architectures exist
- When you want to surface trade-offs before committing
- Use inside
/devPhase 2 (brainstorm phase) or standalone
What it does
Source of truth: ~/Agents/agents/brainstorm.md
Uses the brainstorm agent to produce exactly 3 concrete options:
- Each option has: approach name, description, pros, cons, and effort estimate
- Ends with a recommended option + rationale
- Does not start coding — outputs decision material only
Usage
/brainstorm add rate limiting to the API
/brainstorm how to handle session state
/brainstorm architecture for the new notification system
Note
If $ARGUMENTS is present, use it as the topic. Otherwise ask:
What are we brainstorming? (one-line description of the design question)
Wait for answer.
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.
- yesterday First seen · 50 lines · 12 tokens per session scan A 9b9727cc1ffb
brainstorm is a command published in the GitHub repository AKSoftCode/aicrew (3 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 325 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.
Other commands, from other repositories
implement
Execute implementation by processing atomic task files one at a time with Context Pinning (Atomic Traceability Model).
plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
clarify
Pre-plan interview — resolves spec ambiguity (v0.1 contract), pins the architectural lurkers from .specify/knowledge/architectural-lurkers.yaml, fires trigger-driven probes from .specify/knowledge/triggers.yaml, walks compliance scope, and writes decisions to specs/defaults/registry.yaml with provenance tagging.
cleanup
Detect and remove orphaned code, unused components, dead routes, and stale database artifacts.
registry
Discover, create, or update the Project Defaults Registry. Scans project manifests (package.json, pyproject.toml, Cargo.toml, go.mod, etc.), batches findings for HITL confirmation, then writes specs/defaults/registry.yaml with a full audit trail in changelog.md.
specify
Create or update the feature specification from a natural language feature description.