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/agent-rig/rignpx agentmods add skills/agent-rig/rig/rig-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/agent-rig/rig/rig-review)<a href="https://agentmods.dev/skills/agent-rig/rig/rig-review"><img src="https://agentmods.dev/badge/skills/agent-rig/rig/rig-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/agent-rig/rig/rig-review"><img src="https://agentmods.dev/badge/skills/agent-rig/rig/rig-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.00142 | $0.04808 |
| Opus 5.5 | $0.00057 | $0.01923 |
| Sonnet 5.5 | $0.00028 | $0.00962 |
| Haiku 4.5 | $0.00014 | $0.00481 |
Grade A, and why
rig-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.
How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rig-review — find and fix, in one skill
Local code review with two verbs:
find(default) — walk the project'sREVIEWER.mdcatalog and the applicable per-scope invariants against a diff with a fresh-contextrevieweragent (two passes), and return a triaged P0–P3 finding list. Read-only — it reports, it doesn't edit.fix— take review feedback and loop acoderagent over it until the review comes back clean (or a round budget is hit). Two feedback sources: a PR review bot on an open PR, or localfindresults.
The point is to pre-empt the PR review bot: every finding caught and fixed
locally is one you don't pay PR round-trip latency on. Implement/epic-style
flows call rig-review find then rig-review fix --source local so the loop
lives in one place.
Configuration
Reads .rig/config.json:
review.patternsFile— the P0–P3 catalog the reviewer walks (default.claude/REVIEWER.md). If absent, fall back to the kit's generic categories (correctness, security/trust-boundary, error-handling, concurrency, API/contract, tests, style) and say so.review.bot— PR review bot to poll/re-trigger:codex,claude, ornone(defaultnone).noneforces the local-only loop forfix.review.botRetrigger— comment that re-triggers the bot (e.g.@codex review). Required whenbotis notnone.review.maxRounds— max fix↔recheck rounds before handing to a human (default5);--rounds Noverrides.vcs.baseRef— diff base when no<base>is given (defaultorigin/main).project.repo—owner/namefor everygh apicall (bot source). Never hardcode; derive from the git remote if unset.agents.reviewer/agents.coder— the project's names for those roles (defaultrig-<role>).style.guideFile— the writing style for findings (default.claude/STYLE.md).
Scope invariants (per-subsystem REVIEWER.md). Beyond the root catalog, a
subsystem may carry its own REVIEWER.md colocated with its code — concrete
correctness invariants it "learned the hard way," each ideally citing the PR
where it was found. scripts/scope-reviewer.ts resolves which apply to a diff
(ancestor-walk + any governs: globs a scope declares). find collects them
and has the reviewer assert each as a P1. No-op if the project ships none.
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 Changed · +26 lines d1bbf65587d9
- 1mo ago First seen · 281 lines · 142 tokens per session scan A 93343ac19fde
rig-review is a skill published in the GitHub repository agent-rig/rig (3 stars, last pushed 1mo ago), licensed MIT. It adds 142 tokens to every session and 4,808 once invoked, about $0.0006 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
code-graph
Navigate indexed code, trace callers and impact, and select Codegraph, specialist graph queries, or document graphs with explicit freshness and source evidence.
independent-review
Review a batch of changes as an independent reviewer who did not write them, before commit or push. Use after a set of edits, after an autonomous loop, or when the user asks for a pre-commit review.
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
gsd-ns-review
quality gates | code review debug audit security eval ui.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…