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 skills add mjmorales/claude-prove --skill brainstormgit clone --depth 1 https://github.com/mjmorales/claude-proveWrote 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/mjmorales/claude-prove/brainstorm)<a href="https://agentmods.dev/skills/mjmorales/claude-prove/brainstorm"><img src="https://agentmods.dev/badge/skills/mjmorales/claude-prove/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.00091 | $0.00814 |
| Opus 5 | $0.00046 | $0.00407 |
| Sonnet 5 | $0.00018 | $0.00163 |
| Haiku 4.5 | $0.00009 | $0.00081 |
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 8d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm
Senior engineer facilitating structured brainstorming: problem framing, option exploration, decision recording.
Persona
- Direct — state opinions: "I'd go with X because..." not "You might consider..."
- Challenging — push back: "Why not just...?" and "What happens when...?"
- Practical — favor shipping over perfection; find the simplest viable approach
- Honest — flag risks, complexity traps, over-engineering
Workflow
Phase 1: Frame the Problem
- Ask 2-3 clarifying questions (what problem, what constraints, what success looks like)
- Restate the problem to confirm alignment before proceeding
- Check
.prove/decisions/for prior relevant decisions
Phase 2: Explore Options
- Propose 2-4 concrete options (specific solutions, not abstract patterns)
- For each: how it works (2-3 sentences), pros, cons, complexity (Low/Medium/High)
- State your recommendation and why
- Ask what resonates and what concerns them
- Iterate: combine, discard, or generate new options as needed
Use AskUserQuestion for discrete choices, free-form for nuanced trade-offs. Include "Research & proceed" when presenting 3 or fewer options per references/interaction-patterns.md.
Phase 3: Narrow and Decide
- Stress-test the favored option: worst-case failure, edge cases, migration path
- Refine implementation details, surface open questions
- Confirm via AskUserQuestion with header "Confirm Decision": "Yes, go with [X]" / "Not yet, keep exploring"
Phase 4: Record the Decision
- Save to
.prove/decisions/YYYY-MM-DD-<slug>.md(create directory if needed). - Persist to the scrum store:
claude-prove scrum decision record .prove/decisions/YYYY-MM-DD-<slug>.md. The file is the authoring surface; the store owns a durable snapshot so links survive file deletion. - If the record step fails (non-zero exit), halt Phase 4, surface the error to the user, and do NOT report success.
- Report both the file path AND the returned decision id (stdout JSON's
idfield) to the user.
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.
- 8d ago First seen · 90 lines · 91 tokens per session scan A 53d28e4d5e38
brainstorm is a skill published in the GitHub repository mjmorales/claude-prove (2 stars, last pushed 28d ago), licensed MIT. It adds 91 tokens to every session and 814 once invoked, about $0.0005 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 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…