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/rodolfochicone/rc-projectWrote 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/rodolfochicone/rc-project/rc-plano)<a href="https://agentmods.dev/commands/rodolfochicone/rc-project/rc-plano"><img src="https://agentmods.dev/badge/commands/rodolfochicone/rc-project/rc-plano.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.1 | $0.00019 | $0.00207 |
| Opus 5 | $0.00010 | $0.00103 |
| Sonnet 5 | $0.00004 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
rc-plano 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 7d 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
Tarefa: $ARGUMENTS
Siga o fluxo recomendado, SEM escrever nem editar código ainda:
- Explore — leia os arquivos, exports, callers imediatos e utilitários relevantes para entender o contexto. Use subagents de busca se precisar varrer muitos arquivos, para não inundar o contexto principal.
- Assunções — liste explicitamente as suposições que está fazendo. Se algo estiver ambíguo, pergunte em vez de adivinhar.
- Plano — apresente um plano de implementação passo a passo: arquivos a criar/editar, ordem, pontos de risco e critérios de sucesso (como verificar que ficou pronto).
- Pare e espere meu OK antes de implementar.
Não faça alterações neste passo. Só depois que eu aprovar o plano você entra no modo de implementação.
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.
- 7d ago First seen · 16 lines · 19 tokens per session scan A 39960f9cec19
rc-plano is a command published in the GitHub repository rodolfochicone/rc-project (19 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 207 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
security-scan
Run AgentShield against agent, hook, MCP, permission, and secret surfaces.
learn
Extract patterns and learnings from current session.
fire-0-orient
Orient on an existing project - understand what's here and what's next.
fire-resurrect
Autonomous Resurrection Mode — reverse-engineer intent from messy code, then rebuild clean from scratch.
fire-brainstorm
Dedicated ideation and exploration before implementation.
fire-1b-research
Research, vision selection, and roadmap generation for a new project (Dominion Flow).