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/int2t05/engineering-skills/brainstormnpx skills add int2t05/engineering-skills --skill brainstormgit clone --depth 1 https://github.com/int2t05/engineering-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/int2t05/engineering-skills/brainstorm)<a href="https://agentmods.dev/skills/int2t05/engineering-skills/brainstorm"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/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 | $0.00075 | $0.01559 |
| Opus 5 | $0.00037 | $0.00779 |
| Sonnet 5 | $0.00015 | $0.00312 |
| Haiku 4.5 | $0.00007 | $0.00156 |
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 5d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm
Sharpen a vague idea into a confirmed proposal through one-question-at-a-time dialogue. The cheapest moment to find ambiguity is before any plan, spec, or code exists — once building starts, switching costs lock in the wrong thing.
When to use
- The ask is underspecified — missing who, why, what success looks like, or the binding constraint.
- New feature, project, or "refine this idea" / "stress-test my thinking."
- User says "brainstorm", "grill me", "interview me", "refine this idea", "头脑风暴", "帮我打磨想法", or "盘问我".
- You're tempted to silently fill ambiguous requirements before a spec exists.
Not for: unambiguous asks ("rename this variable"), pure info requests, or when the user has explicitly asked for speed over verification.
Steps
-
Hypothesize with a confidence number. If in a codebase, explore project context first (Glob/Grep/Read for architecture, patterns, constraints) before forming the hypothesis. Before asking anything, write your best read of what the user wants in one sentence, plus an honest confidence (0–100%):
HYPOTHESIS: You want a way to answer "how are we doing?" in standup, and "dashboard" was the convention that came to mind. CONFIDENCE: ~30% — missing: who it's for, what "metrics" means, what success looks likeBelow ~70%, append what's still unresolved. The number forces honesty — if you can't predict the user's reaction to the next three questions, the number is wrong.
-
Ask ONE question, with a guess attached.
Q: <one focused question> GUESS: <your hypothesis for the answer, with reasoning>One question per message — never a batch. Batching encourages skim-reading and surface answers; the third question often depends on the first. Attach a guess so the user reacts to a wrong hypothesis faster than generating from scratch. Be visibly willing to be wrong.
-
Listen for "want vs. should want." The most dangerous answers pattern-match best-practice talk ("scalable", "clean architecture", "the standard approach") without specifics. When you hear these, ask: "If you didn't have to justify this to anyone, what would you actually want?" That question often does more work than the previous five. For structured problem-validation methods — the Mom Test interview (past behavior, not future opinion), JTBD switching interview, opportunity-solution tree, working backwards / PR-FAQ — load
references/discovery-methods.md.
What ships with it
3 files 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.
- 5d ago First seen · 108 lines · 75 tokens per session scan A 0a2ae1f35f62
brainstorm is a skill published in the GitHub repository int2t05/engineering-skills (3 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 1,559 once invoked, about $0.0004 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
style-direction
Abrir y operar el companion visual de Selina para elegir una direccion de estilo en proyectos con interfaz. Skill manual: levanta un servidor local y escribe artefactos visuales.
incident-response
Protocolo de respuesta ante incidentes en produccion: triaje, mitigacion, causa raiz y postmortem. Usar ante caidas, errores criticos, incidentes de seguridad o degradacion de servicio.
pr-workflow
Crear pull requests completas con descripcion, labels y reviewers.
sync-project-docs
Usar para sincronizar la documentación viva del proyecto después de una fase. También: actualizar docs/project, índice, architecture.md, compliance.md, threat-model.
write-adr
Usar para escribir o cerrar un Architecture Decision Record. También: ADR, docs/adr, decisión de stack, persistencia, autenticación o límites de arquitectura.
compliance-check
Usar para verificar cumplimiento RGPD, NIS2 y CRA. También: verificar RGPD, cumplimiento normativo, NIS2, CRA, Cyber Resilience Act, protección de datos, regulación europea.