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 boparaiamrit/skills-by-amrit --skill brainstorminggit clone --depth 1 https://github.com/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/brainstorming)<a href="https://agentmods.dev/skills/boparaiamrit/skills-by-amrit/brainstorming"><img src="https://agentmods.dev/badge/skills/boparaiamrit/skills-by-amrit/brainstorming/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/skills/boparaiamrit/skills-by-amrit/brainstorming"><img src="https://agentmods.dev/badge/skills/boparaiamrit/skills-by-amrit/brainstorming.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.00034 | $0.01844 |
| Opus 5 | $0.00017 | $0.00922 |
| Sonnet 5 | $0.00007 | $0.00369 |
| Haiku 4.5 | $0.00003 | $0.00184 |
Grade A, and why
brainstorming 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Ideas Into Designs
Overview
Turn rough ideas into validated designs through collaborative dialogue before a single line of code is written.
Core principle: Understand what you're building before you build it.
Violating the letter of this process is violating the spirit of this process.
The Iron Law
NO IMPLEMENTATION WITHOUT A VALIDATED DESIGN FIRST
If you haven't clarified requirements and gotten design approval, you cannot write code.
When to Use
Always:
- New feature requests
- Significant refactors
- New projects or modules
- Major behavior changes
- Architecture decisions
Exceptions (ask your human partner):
- Bug fixes with clear reproduction
- Typo corrections
- Dependency updates
- Configuration changes
When NOT to Use
- You already have a detailed design document (use
writing-plans) - The task is a bug fix with clear reproduction steps (use
systematic-debugging) - The task is a simple configuration change or file edit
- The user explicitly says "just do it, no discussion needed"
Anti-Shortcut Rules
YOU CANNOT:
- Start coding before design approval — even "just to prototype"
- Assume requirements the user hasn't stated — ask, even if it feels obvious
- Present only one approach — always offer 2-3 with trade-offs
- Skip edge cases — "what happens when this fails?" is always relevant
- Design for scale you don't need — YAGNI unless the user requests otherwise
- Accept vague requirements — "make it better" is not a requirement
- Let your bias override the user's intent — recommend, don't dictate
- Skip the "Risks and Unknowns" section — there are always unknowns
Common Rationalizations (Don't Accept These)
| Rationalization | Reality |
|---|---|
| "This is obvious, no need to brainstorm" | Obvious to you ≠ obvious to the codebase. Ask first. |
| "I'll figure out the design as I code" | That's not brainstorming, that's hoping. Plan first. |
| "The user knows what they want" | Users know the PROBLEM. They rarely know the best SOLUTION. |
| "We can change it later" | Changing architecture later costs 10x. Design now. |
| "Let me just build a quick prototype" | Prototypes become production code. Design first. |
| "The requirements are simple" | Simple requirements hide complex edge cases. Explore them. |
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 · 253 lines · 34 tokens per session scan A 51efddd65150
brainstorming is a skill published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,844 once invoked, about $0.0002 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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…