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 skills add Zate/cc-plugins --skill reviewgit clone --depth 1 https://github.com/Zate/cc-pluginsWrote 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/skills/zate/cc-plugins/review)<a href="https://agentmods.dev/skills/zate/cc-plugins/review"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/review/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/skills/zate/cc-plugins/review"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/review.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.00015 | $0.00523 |
| Opus 5.5 | $0.00006 | $0.00209 |
| Sonnet 5.5 | $0.00003 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
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 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
Review - Code Review
Comprehensive code review for changes, PRs, or specific files. You do the work directly.
Step 1: Identify Scope
AskUserQuestion:
questions:
- question: "What would you like to review?"
header: "Scope"
multiSelect: false
options:
- label: "Uncommitted changes"
description: "Review git diff"
- label: "Staged changes"
description: "Review git diff --cached"
- label: "Recent commits"
description: "Review last few commits"
- label: "Specific files"
description: "I'll specify paths"
Step 2: Gather Code
git diff # Uncommitted
git diff --cached # Staged
git log -p -n 3 # Recent commits
gh pr diff [number] # PR
Step 3: Review
Check these areas directly:
Correctness
- Logic errors, edge cases, error handling
Security
- Input validation, no hardcoded secrets, injection risks
Quality
- Clear naming, no duplication, appropriate comments
Performance
- No N+1 queries, proper resource handling
Step 4: Report
Present findings by severity:
## Code Review
### Critical (Must Fix)
- [Issue]: [Location] - [Problem and fix]
### High Priority
- [Issue]: [Location] - [Problem and fix]
### Suggestions
- [Minor improvements]
### Positive
- [Good patterns observed]
Step 5: Next Steps
AskUserQuestion:
questions:
- question: "Review complete. How proceed?"
header: "Action"
multiSelect: false
options:
- label: "Fix critical"
description: "Address blockers only"
- label: "Fix all"
description: "Apply all suggested fixes"
- label: "Accept as-is"
description: "Proceed without changes"
If fixing, make the changes directly using Edit tool.
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 · 102 lines · 15 tokens per session scan A 04e3fbc5f2d4
review is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 523 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-08-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…