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/refresh)<a href="https://agentmods.dev/commands/vynazevedo/first-plan/refresh"><img src="https://agentmods.dev/badge/commands/vynazevedo/first-plan/refresh/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/refresh"><img src="https://agentmods.dev/badge/commands/vynazevedo/first-plan/refresh.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.00035 | $0.01094 |
| Opus 5.5 | $0.00014 | $0.00438 |
| Sonnet 5.5 | $0.00007 | $0.00219 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
refresh 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fp:refresh
Atualização incremental da camada compilada.
Argumentos
$ARGUMENTS:
- vazio: atualiza só seções marcadas como stale
- nome de seção (e.g.,
01-topology): força refresh dessa seção --all: força refresh completo (equivalente a/fp:init --forcemas preserva backups)
Workflow
Passo 1 - Pre-flight
Verificar .first-plan/ existe. Se não, orientar a rodar /fp:init primeiro.
Passo 2 - Determinar escopo
- Ler
.first-plan/08-meta/cache.jsonpara identificar arquivos com hash diferente (modificados desde último init/refresh) - Ler
.first-plan/08-meta/coverage.mdseção "Stale" para arquivos marcados pelo hook - Mapear arquivos modificados → seções afetadas:
| Arquivo modificado | Seções afetadas |
|---|---|
| Manifesto (go.mod/package.json/etc) | 01-topology/stacks |
cmd/, entry points |
01-topology/architecture |
| Handlers / routers | 01-topology/boundaries |
| Dockerfile, .github/workflows | 01-topology/deployments |
| Qualquer código (>= 5 arquivos) | 01-topology/activity, 02-conventions/* |
| pkg/, lib/, utils/ | 03-reuse/* |
| Models, types | 04-domain/entities |
| Flows críticos (handlers de domínio) | 04-domain/flows |
| Tests | 02-conventions/testing, 05-risks/untested |
| Config files (lint, format) | 02-conventions/* |
| docs/, specs/ | 09-features/* |
Se $ARGUMENTS é nome de seção, force apenas essa.
Passo 3 - Refresh por seção
Para cada seção a atualizar:
01-topology/* (excluindo activity, ownership)
Spawnar discovery-analyst com escopo restrito (apenas reanalisar essa seção).
01-topology/activity, 01-topology/ownership
Inline - rodar comandos git novamente.
02-conventions/, 06-rationale/
Spawnar pattern-archeologist com categories=[<seção específica>].
03-reuse/*
Spawnar discovery-analyst com escopo reuse-only.
04-domain/*
Spawnar discovery-analyst com escopo domain-only.
05-risks/*
Spawnar discovery-analyst com escopo risks-only.
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 · 125 lines · 35 tokens per session scan A f7ab7ffcf031
refresh is a command published in the GitHub repository vynazevedo/first-plan (24 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,094 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:off
🍵 Disable matcha — completely silent, zero token overhead.
resume
Resume an interrupted HOTL workflow run.
what-happened
Summarize recent activity from the recording session.
atomic-help
Route a lost user to the right atomic verb, skill, agent, or binary subcommand. Bare invocation reads git state and recommends one next step. Topic keyword or freeform intent → focused pointer. tour → guided walkthrough of the system. Help router, not duplicated docs.
follow-up
Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.