Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/salavender/antigravity-compound-engineering-pluginnpx agentmods add skills/salavender/antigravity-compound-engineering-plugin/code-reviewWrote 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/salavender/antigravity-compound-engineering-plugin/code-review)<a href="https://agentmods.dev/skills/salavender/antigravity-compound-engineering-plugin/code-review"><img src="https://agentmods.dev/badge/skills/salavender/antigravity-compound-engineering-plugin/code-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/salavender/antigravity-compound-engineering-plugin/code-review"><img src="https://agentmods.dev/badge/skills/salavender/antigravity-compound-engineering-plugin/code-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.00328 |
| Opus 5.5 | $0.00006 | $0.00131 |
| Sonnet 5.5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
code-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.
This is a copy
100% identical to code-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Code Review Skill
Overview
A systematic approach to code review that moves beyond "it looks good" to rigorous quality verification. This skill provides specific checklists and procedures for different review types.
When To Use
- Self-Review: Before submitting a PR or finishing
/work - Peer Review: When reviewing another agent's or human's code (
/resolve_pr) - Plan Review: When validating an implementation plan (
/plan_review)
Instrumentation
# Log usage when using this skill
./scripts/log-skill.sh "code-review" "manual" "$$"
What do you want to do?
- Security Review (Auth, RLS, Input) →
workflows/security-pass.md - Performance Review (Database, Re-renders) →
workflows/performance-pass.md - Architecture Review (State, Data Flow) →
workflows/architecture-pass.md - General Quality Check →
checklists/pre-merge.md
Key Principles
- Review in Passes: Don't check everything at once. Do a security pass, then a performance pass, etc.
- Reference Patterns: Always check against
docs/solutions/patterns/critical-patterns.md. - Verify, Don't Guess: If you see a potential issue, verify it with a quick test or script.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 38 lines · 15 tokens per session scan A 2898c62511b2
code-review is a skill published in the GitHub repository salavender/antigravity-compound-engineering-plugin (48 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 328 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to code-review, differing in 0 lines, and is treated as a copy.
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"…
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…
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…
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…