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/nota-america/forgecat-agent-profilesWrote 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/nota-america/forgecat-agent-profiles/brainstorm)<a href="https://agentmods.dev/commands/nota-america/forgecat-agent-profiles/brainstorm"><img src="https://agentmods.dev/badge/commands/nota-america/forgecat-agent-profiles/brainstorm.svg" alt="Measured on agentmods" 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.01437 |
| Opus 5 | $0.00000 | $0.00718 |
| Sonnet 5 | $0.00000 | $0.00287 |
| Haiku 4.5 | $0.00000 | $0.00144 |
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 4d 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.
This is a copy
95% identical to brainstorm — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 115 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 (
.forgecat/profiles/@forgecat/anthropics_knowledge-work-plugins_product-management/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.
- 4d ago First seen · 115 lines · 0 tokens per session scan A c4c6fad65f3d
brainstorm is a command published in the GitHub repository nota-america/forgecat-agent-profiles (65 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,437 tokens. A static security scan graded it A with 0 findings. It is 95% identical to brainstorm, differing in 8 lines, and is treated as a copy.
Other commands, from other repositories
add-note
Add an internal or external note to a ConnectWise PSA ticket.
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.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
speckit.spec-stats.open
On-demand view of everything not complete: what stage each is stuck at, what the immediate next artifact/command is, oldest-untouched first, stale warnings past staleafterdays.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
user-story-sprint
Plan a sprint by selecting stories based on capacity, dependencies, and priority.