Knowledge Work Plugins is an open-source collection of Claude extensions organized around roles such as productivity, sales, and customer support. Each plugin combines role-specific guidance, connectors, commands, and sub-agents so knowledge workers can use Claude with their team’s tools and processes. The catalogue entries are examples of, or workflows from, this plugin collection.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/anthropics/knowledge-work-pluginsnpx agentmods add commands/anthropics/knowledge-work-plugins/brainstormWrote 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/anthropics/knowledge-work-plugins/brainstorm)<a href="https://agentmods.dev/commands/anthropics/knowledge-work-plugins/brainstorm"><img src="https://agentmods.dev/badge/commands/anthropics/knowledge-work-plugins/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/anthropics/knowledge-work-plugins/brainstorm"><img src="https://agentmods.dev/badge/commands/anthropics/knowledge-work-plugins/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.00017 | $0.01454 |
| Opus 5.5 | $0.00007 | $0.00582 |
| Sonnet 5.5 | $0.00003 | $0.00291 |
| Haiku 4.5 | $0.00002 | $0.00145 |
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 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- brainstorm — 100% identical, 0 lines differ
- brainstorm — 95% identical, 8 lines differ
- brainstorm — 89% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/brainstorm
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Brainstorm a product topic with a sharp, opinionated thinking partner. This is a conversation, not a deliverable — the goal is to push thinking further than the PM would get alone.
Usage
/brainstorm $ARGUMENTS
How It Works
┌────────────────────────────────────────────────────────────────┐
│ BRAINSTORM │
├────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Explore problem spaces and opportunity areas │
│ ✓ Generate and challenge product ideas │
│ ✓ Stress-test assumptions and strategies │
│ ✓ Apply PM frameworks (HMW, JTBD, First Principles, etc.) │
│ ✓ Capture key ideas, next steps, and open questions │
├────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Knowledge base: Pull prior research, specs, and decisions │
│ + Analytics: Ground ideas in actual usage data │
│ + Project tracker: Check what has been tried before │
│ + Chat: Review recent team discussions for context │
└────────────────────────────────────────────────────────────────┘
Workflow
1. Understand the Starting Point
The PM might bring any of these — identify which one and adapt:
- A problem: "Our users drop off during onboarding" — start in problem exploration mode
- A half-formed idea: "What if we added a marketplace?" — start in assumption testing mode
- A broad question: "How should we think about AI in our product?" — start in strategy exploration mode
- A constraint to work around: "We need to grow without adding headcount" — start in solution ideation mode
- A vague instinct: "Something feels off about our pricing" — start in problem exploration mode
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 First seen · 121 lines · 17 tokens per session scan A fb0ce47a71ac
brainstorm is a command published in the GitHub repository anthropics/knowledge-work-plugins (32,620 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 1,454 once invoked, about $0.0001 per session on Opus 5.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-09-05.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.