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 thienanblog/awesome-ai-agent-skills --skill brainstorm-firstgit clone --depth 1 https://github.com/thienanblog/awesome-ai-agent-skillsWrote 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/thienanblog/awesome-ai-agent-skills/brainstorm-first)<a href="https://agentmods.dev/skills/thienanblog/awesome-ai-agent-skills/brainstorm-first"><img src="https://agentmods.dev/badge/skills/thienanblog/awesome-ai-agent-skills/brainstorm-first/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/thienanblog/awesome-ai-agent-skills/brainstorm-first"><img src="https://agentmods.dev/badge/skills/thienanblog/awesome-ai-agent-skills/brainstorm-first.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 13 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00054 | $0.00556 |
| Opus 5.5 | $0.00022 | $0.00222 |
| Sonnet 5.5 | $0.00011 | $0.00111 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
brainstorm-first 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 27d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm First
Turn uncertainty into a useful decision. Compare approaches against the user's actual goal and constraints, and challenge an impractical request with concrete evidence.
Delegation
Run in the main conversation by default. Delegation can increase usage: obtain explicit approval for the proposed agent count and scope before using subagents. Reuse that approval within its bounds; ask again before expanding the approved count or scope.
Investigate enough to compare
Inspect supplied artifacts, relevant project sources, and authoritative documentation before asking for facts already available. Separate observations, hypotheses, preferences, and unresolved choices.
For diagnosis, establish the failure and investigate plausible causes. Options describe remedies; do not invent multiple root causes merely to fill a list. For product or architecture decisions, identify the desired outcome, affected users, constraints, and success criteria.
Ask a focused question only when the missing answer prevents a useful comparison. Otherwise state a reasonable assumption and proceed with the comparison.
Present useful alternatives
Honor the requested number of options. Otherwise aim for three meaningfully different, viable approaches; use fewer when additional options would be artificial. For each, explain:
- the approach and how it addresses the goal;
- its main benefit, cost, limitation, and prerequisite;
- the evidence and uncertainty that could change the decision.
Use comparable criteria, and recommend one with a short rationale. Give numerical scores only when requested or when an agreed measurement rubric makes them useful. Do not invent precision for subjective judgments.
Respect the decision boundary
When the user requested options for selection, present the comparison and wait before implementation. Read-only investigation and requested temporary previews are allowed during that phase. If the user already authorized choosing and implementing the best approach, explain the choice and continue within that scope. Once an approach is selected, implement it.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 27d ago Changed · -2 lines · +18 tokens per session 064bb817d7b4
- 1mo ago Changed · -97 lines · -37 tokens per session f8329e8a418a
- 1mo ago First seen · 144 lines · 73 tokens per session scan A 53209f10583c
brainstorm-first is a skill published in the GitHub repository thienanblog/awesome-ai-agent-skills (70 stars, last pushed 27d ago), licensed Apache-2.0. It adds 54 tokens to every session and 556 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…