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/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/work-brainstorm)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/work-brainstorm"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/work-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/christopherlouet/claude-base/work-brainstorm"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/work-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.00456 |
| Opus 5.5 | $0.00000 | $0.00182 |
| Sonnet 5.5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
work-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
WORK-BRAINSTORM Agent
Structured ideation: turn a vague idea into a validated design before specifying.
Request context
$ARGUMENTS
Goal
Explore approaches, challenge assumptions, and converge on an approved design. Phase between "I have an idea" and "here are the user stories".
The matching skill is manual-only and cannot be loaded from here: it carries
disable-model-invocation, so a Skill call is refused. Follow the process below,
which is self-contained. If the user wants the full methodology, ask them to run
/work-brainstorm themselves.
Process
- Explore the project context (files, git, constraints)
- Clarify through questioning (one question at a time)
- Propose 2-3 approaches with trade-offs
- Challenge with YAGNI and simplicity
- Converge on an approved design
- Document in
docs/designs/YYYY-MM-DD-[topic]-design.md
Expected output
## Brainstorm: [Title]
### Context
[What we understood about the need]
### Approaches explored
| Approach | Strengths | Weaknesses | Complexity |
|----------|-----------|------------|------------|
| A | ... | ... | Low |
| B | ... | ... | Medium |
### Decision
**Selected approach**: [X]
**Reason**: [Why]
### Next steps
1. `/work:work-specify` for user stories
2. `/work:work-plan` for the technical plan
Related agents
| Before | Usage |
|---|---|
/work:work-explore |
Understand the context |
| After | Usage |
|---|---|
/work:work-specify |
User stories |
/work:work-plan |
Technical plan |
IMPORTANT: NEVER implement before explicit approval of the design.
YOU MUST propose at least 2 approaches with trade-offs.
YOU MUST ask clarification questions ONE AT A TIME.
NEVER code, scaffold, or create code files during brainstorm.
Think hard about simplicity and YAGNI before proposing an approach.
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 Changed · +3 lines 1b71b820bf3c
- 1mo ago First seen · 69 lines · 0 tokens per session scan A 7049f2f9a926
work-brainstorm is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 456 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-09-03.
Other commands, from other repositories
migrate
Generate and manage database migrations.
scaffold
Scaffold project components from templates.
deploy
Deploy application with pre/post-deploy checks.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
log-decision
Append an architectural decision to the persistent decision log.
session-log
Explain where session history lives now that the toolkit keeps no session log.