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 commands/vynazevedo/first-plan/statusgit clone --depth 1 https://github.com/vynazevedo/first-planWhat 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.00029 | $0.01058 |
| Opus 5 | $0.00015 | $0.00529 |
| Sonnet 5 | $0.00006 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
status 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 3d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fp:status
Estado da camada .first-plan/ no projeto-alvo.
Argumentos
$ARGUMENTS:
- vazio: status resumido
--verbose: status detalhado por seção
Workflow
Passo 1 - Pre-flight
Verificar .first-plan/ existe. Se não:
.first-plan/ ainda não foi compilado neste projeto.
Para começar: /fp:init
Passo 2 - Ler estado
Ler:
.first-plan/07-state/STATE.md- phase, active_plan, last_session.first-plan/08-meta/coverage.md- cobertura por seção, stale list.first-plan/08-meta/confidence.md- confidence overall e por seção.first-plan/08-meta/questions.md- perguntas abertas.first-plan/09-features/INDEX.md- matriz de features (status breakdown).first-plan/INDEX.md- frontmatter (overall_confidence, generated_at)
Passo 3 - Renderizar status resumido (default)
first-plan status
Projeto: <project_name>
Compilado em: <generated_at> (<X dias atrás>)
Fase atual: <phase>
Cobertura: <X>% das seções preenchidas
Confidence média: <Y> (threshold: 0.7)
Perguntas abertas: <N>
Stale: <K> arquivo(s) (rodar /fp:refresh)
Features:
IMPLEMENTED: <a>
IN_PROGRESS: <b> ← cuidado, evite duplicar
SPEC_ONLY: <c>
NOT_STARTED: <d>
DRIFTED: <e> ← <link>
ABANDONED: <f>
Phantom: <g> ← <link>
Plano ativo: <slug ou "nenhum">
Próxima ação sugerida:
<determinada por fase + estado>
Passo 4 - Mode --verbose
Adicionar:
=== Cobertura por seção ===
01-topology/stacks.md confidence 0.91 ✓
01-topology/architecture.md confidence 0.85 ✓
01-topology/boundaries.md confidence 0.72 ✓
01-topology/activity.md confidence 1.00 ✓
01-topology/ownership.md confidence 0.95 ✓
02-conventions/naming.md confidence 0.88 ✓
02-conventions/errors.md confidence 0.90 ✓
02-conventions/testing.md confidence 0.65 ⚠ baixo
02-conventions/logging.md confidence 0.50 ⚠ baixo - 2 perguntas abertas
... (todas as seções)
=== Stale (mudaram desde último refresh) ===
- src/payment/charge.go (modificado 2h atrás)
- src/auth/jwt.go (modificado ontem)
=== Perguntas abertas ===
Q1 (naming): camelCase vs snake_case em handlers
Q2 (logging): nível default em produção
Q3 (errors): wrapping mandatório ou opcional
Q4 (auth): JWT claim obrigatório vs opcional
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.
- 3d ago First seen · 121 lines · 29 tokens per session scan A 0ddf5a206bc5
status is a command published in the GitHub repository vynazevedo/first-plan (23 stars, last pushed 8d ago), licensed MIT. It adds 29 tokens to every session and 1,058 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 commands, from other repositories
gate
Run the full local gate (fmt, lint, test, build, docs, and fuzz when a parser changed) and report only what failed.
release
Prepare the next release per RELEASING.md — gate, price table, surface audit, changelog — and stop at the tag command.
matcha:review
🍵 Review gate — risk-based code review (L0-L3). Nothing ships until this passes.
matcha:audit
🍵 Stack health check — find overlaps, waste, and risks before they become problems.
matcha:why
🍵 Intent Discovery — problem, goals, success criteria, What → Why → How before touching code.
setup
Generate HOTL adapter files for your team's code assistants (Codex, Cline, Cursor, Copilot).