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/yimwoo/hotl-plugin/brainstormingnpx skills add yimwoo/hotl-plugin --skill brainstorminggit clone --depth 1 https://github.com/yimwoo/hotl-pluginWrote 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/yimwoo/hotl-plugin/brainstorming)<a href="https://agentmods.dev/skills/yimwoo/hotl-plugin/brainstorming"><img src="https://agentmods.dev/badge/skills/yimwoo/hotl-plugin/brainstorming.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.00033 | $0.02731 |
| Opus 5 | $0.00016 | $0.01366 |
| Sonnet 5 | $0.00007 | $0.00546 |
| Haiku 4.5 | $0.00003 | $0.00273 |
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 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HOTL Brainstorming
Overview
Turn ideas into designs with explicit HOTL contracts. Ask questions one at a time. Present design for approval before any implementation.
Process
-
Explore context (cheap preflight first)
Phase 1 — Cheap preflight (Glob only, current project directory):
- If user's message references a doc path → read it
- Check for canonical design docs in
docs/designs/*.md - Check for legacy design docs in
docs/plans/*.md - Check for source code, config manifests, or project-specific config files
- "Relevant context" means: design docs, source code, configuration manifests, or project-specific config. Files like
README.md,.gitignore,LICENSE, and scaffolding boilerplate do not count.
Phase 2 — Branch on result:
- Relevant local context found: Read the most recent 1-2 design docs from canonical or legacy locations, inspect only relevant in-project files, and optionally review recent commits (only if the directory is a git repo).
- No relevant local context found: State: "This appears to be a greenfield or effectively empty project, so I'm skipping deep context scanning and moving to clarifying questions." Proceed directly to step 2.
Hard rule: Never scan parent directories, sibling folders, or workspace-wide paths unless the user explicitly provides a path.
-
Determine scope — decide between
feature,phase, orinitiativebefore the clarifying-questions loop. Scope shapes every downstream step: output path, contract structure, depth of inquiry.Scope choices:
feature— one feature, one bug fix, one refactor. Output:docs/designs/YYYY-MM-DD-<slug>-design.md(dated, tactical).phase— one slice of a multi-phase initiative. Same output family as feature:docs/designs/YYYY-MM-DD-phase-N-<slug>-design.md.initiative— a multi-phase project (v1/v2, platform migration, enterprise rebuild). Output:docs/designs/<topic>.md(undated, durable, strategic).
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 · 175 lines · 33 tokens per session scan A e76db7491a41
brainstorming is a skill published in the GitHub repository yimwoo/hotl-plugin (26 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 2,731 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-08-30.
Other skills, from other repositories
first-plan-co-change-analysis
Skill que constrói o Co-change Graph - "quando arquivo X muda, qual outro arquivo geralmente muda junto?". Use durante Discovery e em /fp:cochange. Baseado em git history. Detecta arquivos co-dependentes que devem ser editados juntos para evitar PRs incompletos. v0.3.0+ usa engine nativo Rust quando disponível…
first-plan-provenance-tracker
Skill que define o schema de proveniência e o sistema de freshness tracking para findings em .first-plan/. Use durante Discovery e refresh para registrar source (file:line@SHA), TTL, confidence inicial e cadeia de supersedeção. Aplica decay de confidence baseado em idade.
first-plan-git-intelligence
Skill que extrai inteligência do git history - heatmap de atividade, ownership, branches/PRs in-flight. Use durante Discovery e em /fp:hot, /fp:owner, /fp:in-flight. Tudo via comandos git read-only.
first-plan-protocol
Esta skill DEVE ser carregada em qualquer comando do plugin first-plan. Define o protocolo PLAN-FIRST (Discovery -> Plan -> Approval -> Execution -> Report), as 7 regras invioláveis e o comportamento esperado em cada fase. Ative quando o usuário invocar /fp: ou mencionar "first-plan", "context compilation", "discovery…
first-plan-reconciliation
Skill que define Spec-Code Reconciliation - matching contínuo entre artefatos de intenção (docs, specs, JIRA, GitHub issues) e implementação (código, testes, PRs). Use durante Discovery e em /fp:check para identificar feature ja implementada, em flight, drifted ou abandonada.
first-plan-semantic-reuse
Skill que faz busca semantica via BM25 sobre o indice de simbolos do projeto. Substitui grep do reuse-index quando o engine nativo esta disponivel. Encontra "preciso de validacao de email" mesmo se a funcao se chama validateEmailRFC. Use durante /fp:reuse e /fp:plan para identificar componentes reusaveis com matching…