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/paruff/uFawkesAIWrote 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/paruff/ufawkesai/review-local)<a href="https://agentmods.dev/commands/paruff/ufawkesai/review-local"><img src="https://agentmods.dev/badge/commands/paruff/ufawkesai/review-local/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/paruff/ufawkesai/review-local"><img src="https://agentmods.dev/badge/commands/paruff/ufawkesai/review-local.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.00010 | $0.00217 |
| Opus 5.5 | $0.00004 | $0.00087 |
| Sonnet 5.5 | $0.00002 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
review-local 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
Review the change before it is committed. This is the same rubric CI's agent review applies, run earlier so findings cost minutes, not a PR round trip.
- Read
REVIEW.mdfirst: its Flag and Skip lists, severity levels and output format. - Diff:
git diff --staged; if nothing is staged,git diff origin/main...HEAD. - Read the linked
docs/ai-sdlc/<feature>/{intent,spec,plan}.md. A diff that traces to none of them is itself a finding. - Report as
REVIEW.mdsays: a verdict line (Cleanor the count by severity), then each finding as severity,file:line, the defect, the concrete failure. Say what you did not check.
Read-only: do not edit files, stage, commit or push. Any HIGH finding blocks the
commit; hand it back to @builder.
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 · 18 lines · 10 tokens per session scan A 1192ef412df4
review-local is a command published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 217 once invoked, about $0.0000 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-10-22.
Other commands, from other repositories
review
Review staged git changes for issues before committing.
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
karpathy-check
Revisa as alterações em stage (ou o último commit) com base nos 4 princípios de codificação do Karpathy. Verifica complexidade, ruído no diff, suposições ocultas e verificação de objetivos. Uso: /karpathy-check [--last-commit].
review
Review code against project rules using the code-reviewer agent.