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 skills/jpoutrin/product-forge/brainstorm-solutionnpx skills add jpoutrin/product-forge --skill brainstorm-solutiongit clone --depth 1 https://github.com/jpoutrin/product-forgeWrote 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/skills/jpoutrin/product-forge/brainstorm-solution)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/brainstorm-solution"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/brainstorm-solution.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.00010 | $0.01406 |
| Opus 5 | $0.00005 | $0.00703 |
| Sonnet 5 | $0.00002 | $0.00281 |
| Haiku 4.5 | $0.00001 | $0.00141 |
Grade A, and why
brainstorm-solution 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brainstorm-solution
Category: Documentation
Usage
proc brainstorm-solution [brief] [--constraints "constraints"] [--docs "doc1,doc2"] [--template template-name] [--help]
Arguments
[brief]: Brief description of the feature/problem to brainstorm (if not provided, will be prompted)--constraints: Any existing constraints or requirements--docs: Comma-separated list of related documentation links--template: Use a predefined template (api-integration, data-migration, performance-optimization)--help: Show this help message
Examples
# Full command with all options
proc brainstorm-solution --brief "Add capacity planning to training scheduler" --constraints "Must integrate with existing booking system" --docs "docs/api.md,specs/booking.md"
# Simplified - will prompt for missing info
proc brainstorm-solution "Add capacity planning to training scheduler"
# Using a template
proc brainstorm-solution --template api-integration --brief "Integrate with payment provider"
# Show help
proc brainstorm-solution --help
Execution Instructions for Claude Code
When this command is run, Claude Code should:
1. Parse Arguments and Show Help if Requested
If --help is provided, display this documentation and exit.
2. Initialize Brainstorming Session
a. If brief not provided as argument, prompt for it:
🧠 Technical Brainstorming Session
What feature or problem would you like to brainstorm?
>
b. If constraints not provided, ask:
Any constraints or requirements? (Press Enter to skip)
>
c. If docs not provided, ask:
Related documentation? (comma-separated paths, Press Enter to skip)
>
3. Create Session Directory
Create directory structure:
docs/tech-brainstorm/YYYY-MM-DD-{feature-slug}/
Where feature-slug is derived from the brief (e.g., "capacity-planning")
4. Interactive Brainstorming Flow
Present the interactive menu:
📋 Brainstorming: {brief}
Available sections:
[1] Data Models & Relationships (primary)
[2] System Components & Interactions (primary)
[3] API Design & Endpoints (secondary)
[4] Technology Choices & Trade-offs (secondary)
[5] Security Considerations
[6] Scalability & Performance
[7] Integration Points
[8] Other Considerations
Commands:
- Enter number to work on section
- 'jump N' to switch sections
- 'preview' to see current progress
- 'suggest' for AI suggestions
- 'diagram' to create visualizations
- 'done' to finish session
Current section: [None]
>
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.
- 2d ago First seen · 230 lines · 10 tokens per session scan A 396e80b6dfc8
brainstorm-solution is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 1,406 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…