roborev is a background code-review system for AI coding agents that checks each Git commit and records findings in a review database. It helps developers catch issues in generated code while they work. Catalogue add-ons connect its findings to agent workflows and can support iterative review and fixing.
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 kenn-io/roborev --skill roborev-design-reviewgit clone --depth 1 https://github.com/kenn-io/roborevWrote 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/kenn-io/roborev/roborev-design-review)<a href="https://agentmods.dev/skills/kenn-io/roborev/roborev-design-review"><img src="https://agentmods.dev/badge/skills/kenn-io/roborev/roborev-design-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/kenn-io/roborev/roborev-design-review"><img src="https://agentmods.dev/badge/skills/kenn-io/roborev/roborev-design-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.00019 | $0.01430 |
| Opus 5 | $0.00010 | $0.00715 |
| Sonnet 5 | $0.00004 | $0.00286 |
| Haiku 4.5 | $0.00002 | $0.00143 |
Grade A, and why
roborev-design-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 10d 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
84% identical to roborev-design-review-branch — 83 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
roborev-design-review
Request a design review for a commit and present the results.
Usage
/roborev-design-review [commit] [--panel <name>|none]
Explicit invocation only
Invocation must be explicit: literal personal /roborev-design-review, or structured
Claude Code skill selection.
Requests such as “review this commit's design” without one of these explicit mechanisms
must use native behavior and must not run roborev.
Sandbox access
roborev uses a local daemon. If a command fails with permission denied, the sandbox may be
blocking access to its loopback port or Unix socket. Retry the same Bash command with
dangerouslyDisableSandbox: true. Do not start or restart the daemon because a sandboxed
status probe cannot reach it.
When NOT to invoke this skill
Do NOT invoke this skill when the user is presenting or pasting existing review results. Messages that contain review findings, verdicts, or summaries are outputs — not requests to start a new review.
IMPORTANT
This skill requires you to execute bash commands to validate the commit and launch the review. The task is not complete until the background review finishes and you present the results to the user.
These instructions are guidelines, not a rigid script. Use the conversation context. Skip steps that are already satisfied. Defer to project-level CLAUDE.md instructions when they conflict with these steps.
Instructions
When the user invokes /roborev-design-review [commit] [--panel <name>|none]:
1. Validate inputs
If a commit ref is provided, use the commit-provided command snippet below; it stores and validates the ref before invoking roborev review.
If validation fails, inform the user the ref is invalid. Do not proceed.
2. Build the command
Construct the review command:
If no commit is specified:
roborev review --wait --type design [--panel <name>|none]
If a commit is specified:
read -r commit <<'ROBOREV_REF'
<commit>
ROBOREV_REF
git rev-parse --verify -- "$commit^{commit}" || exit 1
roborev review "$commit" --wait --type design [--panel <name>|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.
- 10d ago First seen · 163 lines · 19 tokens per session scan A b36017944ebc
roborev-design-review is a skill published in the GitHub repository kenn-io/roborev (1,700 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 1,430 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to roborev-design-review-branch, differing in 83 lines, and is treated as a copy.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
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"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.