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/joncik91/ucai/reviewgit clone --depth 1 https://github.com/Joncik91/ucaiWrote 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/joncik91/ucai/review)<a href="https://agentmods.dev/commands/joncik91/ucai/review"><img src="https://agentmods.dev/badge/commands/joncik91/ucai/review.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.00007 | $0.00909 |
| Opus 5 | $0.00003 | $0.00454 |
| Sonnet 5 | $0.00001 | $0.00182 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
review 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
You are performing a thorough code review using parallel agents for independent analysis.
Context
- Review scope: $ARGUMENTS (default: unstaged changes via
git diff) - Current git status: !
git status - Current git diff: !
git diff HEAD
Skill Loading — MANDATORY
Before starting Phase 2, you MUST load the ucai:code-reviewer skill — this is a code review workflow.
- Load:
Skill(ucai:code-reviewer) - Also load the domain skill matching the code being reviewed:
Skill(ucai:backend),Skill(ucai:frontend), etc. - Apply the skill's guidance when evaluating code quality and conventions
You MUST load at least one skill before proceeding. State which skill(s) you loaded and why.
Phase 1: Scope
Goal: Determine what to review.
Lessons loading: If tasks/lessons.md exists, read it and note any patterns relevant to the code being reviewed. Feed known patterns (common mistakes, project-specific gotchas, past corrections) as context to Phase 2 reviewer agents so they can watch for recurrence. If the file doesn't exist, skip silently.
Actions:
- Create todo list
- If $ARGUMENTS specifies files or a PR, use that scope
- If no arguments, review unstaged changes from git diff
- If no changes found, tell the user and stop
- Find any CLAUDE.md files in the project for guideline reference
- Check for
.claude/project.mdand.claude/requirements.md. If found, read them — pass project conventions and non-functional requirements (security, performance targets) as context to Phase 2 reviewer agents so they can validate against project-level specs. - If
tasks/lessons.mdexists, load it and extract patterns relevant to the review scope — include these in Phase 2 agent prompts
Phase 2: Parallel Review
Goal: Get independent perspectives on the code.
MANDATORY: You MUST use the Task tool to launch 3 reviewer agents in parallel. Do NOT skip agents and review the code yourself — independent parallel review catches issues that single-pass review misses.
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.
- 4d ago First seen · 93 lines · 7 tokens per session scan A f2d6b9d40f58
review is a command published in the GitHub repository Joncik91/ucai (29 stars, last pushed 8d ago), licensed MIT. It adds 7 tokens to every session and 909 once invoked, about $0.0000 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
f5-gate
Quality gate management with evidence collection.
f5-classify
Classify input files by type using content-first analysis, detect gaps, and generate coverage declaration.
f5-implement
Implement features and fix bugs with traceability.
f5-import
Import documents - single, batch, analyze, or schema management.
f5-analytics
View project analytics and metrics.
f5-design
Generate design documents and specifications (D1-D4).