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/askgit 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.00023 | $0.00514 |
| Opus 5 | $0.00012 | $0.00257 |
| Sonnet 5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
ask 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 2d 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:ask
Lista e gerencia perguntas abertas para o humano.
Argumentos
$ARGUMENTS:
- vazio: lista perguntas abertas
--answer Q<n> "resposta": registra resposta para pergunta específica
Workflow
Passo 1 - Pre-flight
Verificar .first-plan/08-meta/questions.md existe.
Passo 2 - Lista (default)
Ler arquivo, mostrar perguntas com answered: false:
Perguntas abertas (<N>)
Q1 [naming]
Arquivos usam camelCase em alguns lugares e snake_case em outros. Qual é a convenção atual?
Sinal observado: internal/userHandler.go vs internal/payment_service.go
Hipóteses:
A) Migração em curso de camelCase -> snake_case
B) Inconsistência histórica sem padrão claro
C) Convenção é por tipo de arquivo
Impacto: afeta nomeação de novos arquivos
Q2 [errors]
...
Para responder uma pergunta:
/fp:ask --answer Q1 "snake_case é o padrão atual, camelCase é legacy a migrar"
Passo 3 - Mode --answer
- Ler
08-meta/questions.md - Localizar
Q<n> - Atualizar:
answered: trueanswer: "<texto da resposta>"answered_at: <timestamp>
- Atualizar contadores no frontmatter (
open_questions,answered_questions) - Confirmar: "Q respondida. Considere /fp:refresh para aplicar a resposta nas seções afetadas."
Passo 4 - Aplicar respostas em refresh
A resposta não modifica automaticamente as seções do .first-plan/. O usuário deve rodar /fp:refresh em seguida, e os subagents vão considerar as respostas em questions.md quando reanalisar.
Cuidados
- Não inventar respostas se o usuário pediu a lista vazia ("não há perguntas abertas").
- Não modificar status de pergunta sem confirmação.
- Histórico de perguntas respondidas vai pra seção "Perguntas respondidas" do mesmo arquivo, mantida em ordem cronológica reversa.
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.
- 2d ago First seen · 66 lines · 23 tokens per session scan A f225de609ad2
ask is a command published in the GitHub repository vynazevedo/first-plan (23 stars, last pushed 8d ago), licensed MIT. It adds 23 tokens to every session and 514 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).