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.
git clone --depth 1 https://github.com/vynazevedo/first-planWrote 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/commands/vynazevedo/first-plan/hot)<a href="https://agentmods.dev/commands/vynazevedo/first-plan/hot"><img src="https://agentmods.dev/badge/commands/vynazevedo/first-plan/hot/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/commands/vynazevedo/first-plan/hot"><img src="https://agentmods.dev/badge/commands/vynazevedo/first-plan/hot.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.00025 | $0.00515 |
| Opus 5.5 | $0.00010 | $0.00206 |
| Sonnet 5.5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
hot 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.
What it actually says
/fp:hot
Heatmap de atividade.
Argumentos
$ARGUMENTS:
- vazio: window de 30 dias (default)
--days N: window customizado (e.g.,--days 7,--days 90)
Workflow
Passo 1 - Pre-flight
Verificar git repo. Verificar .first-plan/01-topology/activity.md existe.
Passo 2 - Render
Para window default (30 dias): ler activity.md.
Para window customizado: rerun inline:
git log --since="N days ago" --name-only --pretty=format: | grep -v '^$' | sort | uniq -c | sort -rn | head -20
Passo 3 - Apresentar
Hot zones - últimos <N> dias
Top 20 arquivos:
47 internal/payment/charge.go (refator em curso?)
31 internal/handler/order.go
28 src/components/Cart.tsx
...
Top 20 pastas:
127 internal/payment/ hot zone ⚠
89 src/components/ hot zone ⚠
67 internal/handler/
...
Hot zones (>= 10 commits):
- internal/payment/ - 127 commits (intensa atividade)
- src/components/ - 89 commits (provavelmente UI sendo polida)
Frozen zones (sem commits > 180 dias):
- internal/legacy/ - silencioso ha 8 meses
- pkg/oldauth/ - silencioso ha 14 meses (candidato dead code?)
Implicações:
- Padrões em hot zones podem estar em transição - olhar últimos commits, não histórico antigo
- Frozen zones têm padrões antigos e estáveis
- Mexer em hot zones = alta chance de conflito com PRs em flight (ver /fp:in-flight)
Passo 4 - Conexão com outras camadas
Sugestões automáticas:
- Se algum hot zone tem feature DRIFTED associada: alertar
- Se algum hot zone tem ownership claro: mostrar dono
- Se algum hot zone tem PR em flight: linkar
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 · 69 lines · 25 tokens per session scan A 79b7d4aa13bb
hot is a command published in the GitHub repository vynazevedo/first-plan (24 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 515 once invoked, about $0.0001 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 commands, from other repositories
matcha:status
🍵 Master session health dashboard — intensity, git diff stats, test status, and marker ledger.
worktree
Create a git worktree for isolated feature/fix work.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
resume-project
Run resume-project now — Now / Blocked / Next. Not a cheat sheet.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.