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/ShaheerKhawaja/ProductionOSWrote 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/shaheerkhawaja/productionos/brainstorming)<a href="https://agentmods.dev/commands/shaheerkhawaja/productionos/brainstorming"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/brainstorming/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/shaheerkhawaja/productionos/brainstorming"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/brainstorming.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.00033 | $0.00466 |
| Opus 5 | $0.00016 | $0.00233 |
| Sonnet 5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
brainstorming 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 9d 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
/brainstorming — Idea Exploration
Turn ideas into fully formed designs through collaborative dialogue.
Step 0: Preamble
Run templates/PREAMBLE.md.
Process
Phase 1: Understand
- Check current project context (files, docs, git log)
- Ask clarifying questions one at a time
- Prefer multiple choice when possible
- Focus on: purpose, constraints, success criteria, users
Phase 2: Explore Approaches
- Propose 2-3 different approaches with trade-offs
- Lead with your recommendation and reasoning
- Present options conversationally
- Include effort estimates (human time vs AI time)
Phase 3: Present Design
- Present the design section by section
- Scale each section to its complexity (few sentences if simple, detailed if nuanced)
- Ask after each section: "Does this look right so far?"
- Cover: architecture, components, data flow, error handling, testing
Phase 4: Self-Eval on Design
Run templates/SELF-EVAL-PROTOCOL.md on the design:
- Is it specific enough to implement?
- Does it address all requirements?
- Are edge cases covered?
- Is it the simplest solution that works?
Phase 5: Transition
Once approved, invoke /writing-plans to create the implementation plan. The design becomes the spec.
Key Principles
- One question at a time — Don't overwhelm
- YAGNI ruthlessly — Remove unnecessary features
- Incremental validation — Get approval before moving on
- Design for isolation — Each unit has one clear purpose
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.
- 9d ago First seen · 56 lines · 33 tokens per session scan A f846e9c02979
brainstorming is a command published in the GitHub repository ShaheerKhawaja/ProductionOS (8 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 466 once invoked, about $0.0002 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
settings
View or edit fellowship configuration (/.claude/fellowship.json). Run /settings to see current settings, change values, or reset to defaults.
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
rekindle
Recover a fellowship after a session crash. Scans worktrees and quest state, presents a recovery dashboard, and re-spawns Gandalf with recovered quest context. Use when returning to a crashed or expired fellowship session.
validate-docs
Validate that site and README documentation is current. Report-only — flags issues without modifying anything.
chronicle
One-time codebase onboarding — interactively extracts your team's conventions, identifies reference files, and generates CLAUDE.md sections so Claude codes the way your team does. Run once per project.
scribe
Create a reusable quest template for a specific type of task (e.g., "API endpoint", "migration"). Encodes project-specific rules and conventions into phase guidance that loads automatically during quests.