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/riskgit 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/risk)<a href="https://agentmods.dev/commands/vynazevedo/first-plan/risk"><img src="https://agentmods.dev/badge/commands/vynazevedo/first-plan/risk.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.00029 | $0.00499 |
| Opus 5 | $0.00015 | $0.00249 |
| Sonnet 5 | $0.00006 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
risk 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.
What it actually says
/fp:risk
Riscos catalogados em .first-plan/05-risks/ para um path específico.
Argumentos
$ARGUMENTS - path de arquivo ou pasta.
Workflow
Passo 1 - Pre-flight
Verificar .first-plan/05-risks/* existe.
Passo 2 - Buscar matches
Para cada arquivo em 05-risks/:
fragile.md- listas de items frágeisuntested.md- items sem testesmagic.md- código cleverdebt.md- TODOs/FIXMEs
Match por path:
- Exato: caminho idêntico
- Prefixo: o path solicitado é prefixo de algum item listado
- Regex pattern (se item é wildcard tipo
internal/legacy/*)
Também consultar:
01-topology/activity.md- hot zone implica volatilidade01-topology/ownership.md- sem dono claro = risco09-features/INDEX.md- feature em DRIFTED associada ao path
Passo 3 - Apresentar
Riscos para <path>
Frágil: <Sim/Não>
<detalhe se sim>
Sem testes: <%>
<detalhe>
Magic / clever code: <Sim/Não>
<exemplos se sim>
Débito catalogado:
- TODOs: <count>
- FIXMEs: <count>
- HACKs: <count>
Sinais adicionais:
- Hot zone? <Sim/Não> (X commits em 30 dias)
- Owner: <inferido ou "no clear owner">
- Features afetadas: <linkar 09-features se aplicável>
Recomendação:
<síntese baseada nos sinais>
Passo 4 - Sem riscos catalogados
Nenhum risco específico catalogado para <path>.
Isso pode significar:
- Path realmente seguro
- Discovery não cobriu este path (ver 08-meta/coverage.md)
Para garantir: /fp:refresh
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 · 78 lines · 29 tokens per session scan A 7ce88e56339d
risk is a command published in the GitHub repository vynazevedo/first-plan (23 stars, last pushed 9d ago), licensed MIT. It adds 29 tokens to every session and 499 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
selfreview
Self code review before a release — four narrow reviewers over the change (or the whole repo), findings ranked, nothing edited.
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: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.
pr-review
Review a PR across multiple dimensions (description, code, scan, tests).