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/caiaffa/claude-code-ultimate-engineering-systemWrote 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/caiaffa/claude-code-ultimate-engineering-system/rfc)<a href="https://agentmods.dev/commands/caiaffa/claude-code-ultimate-engineering-system/rfc"><img src="https://agentmods.dev/badge/commands/caiaffa/claude-code-ultimate-engineering-system/rfc/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/caiaffa/claude-code-ultimate-engineering-system/rfc"><img src="https://agentmods.dev/badge/commands/caiaffa/claude-code-ultimate-engineering-system/rfc.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.00014 | $0.00401 |
| Opus 5.5 | $0.00006 | $0.00160 |
| Sonnet 5.5 | $0.00003 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
rfc 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.
What it actually says
Use this for significant technical decisions — architecture changes that affect other teams, new technology, anything over ~2 weeks of work. This is Kovi's standard process (RFC-0001). For small local decisions, use /adr instead.
RFC subject: $ARGUMENTS
Phase 1 — Draft (sequential)
principal-engineer drafts the RFC:
- Fill
~/.claude/engineering/RFC_TEMPLATE.mdcompletely (PT-BR body; identifiers, commands, and service names in English). - All mandatory sections; at least 2 real alternatives (no strawmen).
- Success metrics with baseline and target. People identified by @kovi.com.br email.
- Ask the user for the next RFC number if unknown — do not guess it.
Phase 2 — Challenge (sequential)
architecture-challenger attacks the draft: weakest assumptions, failure modes, distributed risks, alternatives dismissed too fast, impact and implementation-plan gaps. Then run the RFC's own "Checklist de Qualidade".
Phase 3 — Revise & persist (sequential)
principal-engineer revises with the findings (or returns to Phase 1 if
critical issues remain) and returns the full text. The orchestrator writes
it to ~/code/kovi/staff/claude/vault/rfcs/rfc-XXXX-<slug>.md,
Status: "Proposto".
Handoff to Kovi's official process
The system DRAFTS and REFINES the RFC. The official RFC process stays yours:
take the draft from the vault to the kovi-docs repo at
docs/rfc/rfc-XXXX-titulo.md, open the PR, notify on Slack, and run the review.
The system never opens the kovi-docs PR for you.
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 · 35 lines · 14 tokens per session scan A b1826351c67d
rfc is a command published in the GitHub repository caiaffa/claude-code-ultimate-engineering-system (17 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 401 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-09-15.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.