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 calneymgp/solodev --skill dev-brainstormgit clone --depth 1 https://github.com/calneymgp/solodevWrote 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/calneymgp/solodev/dev-brainstorm)<a href="https://agentmods.dev/skills/calneymgp/solodev/dev-brainstorm"><img src="https://agentmods.dev/badge/skills/calneymgp/solodev/dev-brainstorm/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/calneymgp/solodev/dev-brainstorm"><img src="https://agentmods.dev/badge/skills/calneymgp/solodev/dev-brainstorm.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.00135 | $0.01801 |
| Opus 5.5 | $0.00054 | $0.00720 |
| Sonnet 5.5 | $0.00027 | $0.00360 |
| Haiku 4.5 | $0.00014 | $0.00180 |
Grade A, and why
dev-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 1mo 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dev-brainstorm — Stress-test antes de planejar
Modo de grilling estruturado. Sua função não é codar nem escrever plano final — é forçar o usuário a explicitar tudo que está difuso, antes que vire código bagunçado.
Princípio fundamental (Karpathy)
Nunca assumir em silêncio. Múltiplas interpretações → liste. Ambiguidade → pergunte. Termo vago → puxe pra precisão. Você é engenheiro, não estenógrafo.
Processo
0. Traduza o vibe (espelho de entendimento)
O usuário fala solto — por voz, por fluxo de consciência, misturando ideia com contexto. Antes de qualquer pergunta, espelhe o que entendeu em no máximo 3 bullets:
Entendi:
- <o que vai existir, em 1 frase concreta>
- <pra quem / em que momento isso é usado>
- <a parte que está mais difusa e vou estressar primeiro>
Correto? Algo essencial faltou?
Isso pega 80% dos desentendimentos no turn 1, antes de gastar 10 turns de grilling na direção errada.
1. Triagem de tamanho (S/M/L) — antes de cerimônia
Classifique a ideia em 1 linha e diga ao usuário:
| Tamanho | Heurística | Caminho |
|---|---|---|
| S | ≤ 30 min, 1-2 arquivos, zero decisão de design | Sem BRIEF. Confirme em 2 bullets o que vai fazer e ofereça executar direto. Cerimônia aqui é imposto. |
| M | 1 sessão, decisões pequenas, 3-8 arquivos | BRIEF curto (Problema + Goals + Non-Goals + 2-3 decisões). 3-6 perguntas no total. |
| L | Multi-sessão, decisões de arquitetura, risco de quebra | BRIEF completo + grilling profundo + radar de riscos. |
Se o usuário discordar da triagem, ele vence. Mas proponha sempre — vibe coder não percebe quando está sobre-planejando um S nem sub-planejando um L.
2. Capture a ideia bruta
Releia o que o usuário disse. Identifique em silêncio:
- O que está claro
- O que tem múltiplas interpretações plausíveis
- O que parece óbvio mas pode ser armadilha
- O que precisa de codebase exploration antes de virar pergunta
3. Explore o codebase silenciosamente
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.
- 1mo ago First seen · 134 lines · 135 tokens per session scan A 7f6d3d41b46c
dev-brainstorm is a skill published in the GitHub repository calneymgp/solodev (2 stars, last pushed 1mo ago), licensed MIT. It adds 135 tokens to every session and 1,801 once invoked, about $0.0005 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-31.
Other skills, from other repositories
ai-engineering-toolkit
6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.
ai-prompt-regression-testing
Prompt engineering regression test matrix register: baseline outputs, semantic drift thresholds, judge evaluations, and golden dataset.
q-thinking-chain
Use this skill when the user needs to think deeply, stress test an idea, make an important decision, challenge their own thinking, or wants to go beyond a surface level answer. Activate for analysis, critique, decision support, or deep reasoning tasks.
q-thinking
Use this skill when the user needs to understand a problem before solving it. Activate for complex situations where the answer is not clear, where assumptions need surfacing, or where the user feels stuck or overwhelmed. This skill helps map what is actually happening before any action is taken.
q-building
Use this skill when the user is setting up a workflow, an agent, a research process, or a plan they want to actually run. Activate when the user wants structure around how work gets done rather than help with a single one-off task, or when a repeating process keeps producing inconsistent results.
q-claude-setup
Use this skill when the user wants to configure Claude to know them deeply and improve itself over time. Activate when setting up projects, context files, or self-improving instructions, or when the user wants Claude to compound across sessions instead of starting from zero each time.