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/using-hotlnpx skills add yimwoo/hotl-plugin --skill using-hotlgit 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/using-hotl)<a href="https://agentmods.dev/skills/yimwoo/hotl-plugin/using-hotl"><img src="https://agentmods.dev/badge/skills/yimwoo/hotl-plugin/using-hotl.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.00025 | $0.00879 |
| Opus 5 | $0.00013 | $0.00439 |
| Sonnet 5 | $0.00005 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
using-hotl 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 4d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use HOTL Skills
HOTL skills are for code-changing tasks that require planning — new features, refactors, and significant changes. Not every task needs a skill.
Answer directly without invoking a skill:
- Code understanding questions — "how does this work?", "where is this defined?", "explain this error"
- Quick fixes — typos, config values, import paths, obvious one-line corrections
- Error tracing — "what does this error mean?", "which file throws this?"
Use hotl:systematic-debugging (no brainstorm/plan needed):
- Bug investigations, test failures, unexpected behavior
Use the full HOTL workflow (brainstorm → plan → execute):
- New features, significant refactors, architectural changes
Available HOTL Skills
Invoke any of these when appropriate:
| Skill | When to Use |
|---|---|
hotl:brainstorming |
Before any feature work — design with HOTL contracts |
hotl:writing-plans |
After design approval — produces docs/plans/YYYY-MM-DD-<slug>-workflow.md |
hotl:governed-execution |
Preferred execution entry point — selects host driver/profile while preserving renewable ownership, bounded loops, effect evidence, and receipts |
hotl:executing-plans |
Linear execution with human checkpoints |
hotl:loop-execution |
Execute a workflow file with loops + auto-approve |
hotl:subagent-execution |
Delegated step runner over the loop execution engine — delegates eligible steps to fresh subagents |
hotl:dispatch-agents |
2+ independent tasks that can run in parallel |
hotl:finishing-a-development-branch |
After execution — merge back, publish/PR, keep, or discard the execution branch/worktree |
hotl:tdd |
Before writing any implementation code |
hotl:systematic-debugging |
When encountering any bug or unexpected behavior |
hotl:skill-authoring |
When creating, editing, or reviewing HOTL skills, agents, commands, or behavior-shaping instructions |
hotl:document-review |
Optional — review existing docs, external specs, or hand-authored plans |
hotl:requesting-code-review |
Dispatched by executors at review checkpoints — standardizes what context the reviewer receives |
hotl:receiving-code-review |
Invoked when review findings arrive — verify, evaluate against contracts, then implement |
hotl:code-review |
After completing implementation, before merging |
hotl:pr-reviewing |
Review a PR across multiple dimensions — description, code, scan, tests |
hotl:resuming |
Resume an interrupted workflow run with verify-first effect recovery and explicit ownership takeover/handoff |
hotl:verification-before-completion |
Before claiming work is done |
hotl:setup-project |
To generate adapter files for Codex, Cline, Cursor, Copilot |
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.
- 4d ago First seen · 64 lines · 25 tokens per session scan A 1fafde6a32b6
using-hotl is a skill published in the GitHub repository yimwoo/hotl-plugin (26 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 879 once invoked, about $0.0001 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…