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-review-branchgit 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-review-branch)<a href="https://agentmods.dev/skills/kenn-io/roborev/roborev-review-branch"><img src="https://agentmods.dev/badge/skills/kenn-io/roborev/roborev-review-branch/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-review-branch"><img src="https://agentmods.dev/badge/skills/kenn-io/roborev/roborev-review-branch.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.00021 | $0.02095 |
| Opus 5 | $0.00010 | $0.01047 |
| Sonnet 5 | $0.00004 | $0.00419 |
| Haiku 4.5 | $0.00002 | $0.00210 |
Grade A, and why
roborev-review-branch 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.
This is a copy
97% identical to roborev-design-review-branch — 109 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
roborev-review-branch
Request a code review for all commits on the current branch and present the results.
Usage
/roborev-review-branch [--base <branch>] [--type security|design] [--panel <name>|none]
Explicit invocation only
Invocation must be explicit: literal personal /roborev-review-branch, or structured
Claude Code skill selection.
Requests such as “review this branch” 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 inputs 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-review-branch [--base <branch>] [--type security|design] [--panel <name>|none]:
1. Validate inputs
If a base branch is provided, use the base-branch command snippet below; it stores and validates the ref before invoking roborev review.
The snippet recovers one case on its own: when the ref names a configured remote followed by a branch (for example upstream/main) and that remote-tracking ref has not been fetched into this worktree yet, it fetches that one branch from that one remote and re-validates. It searches configured remote names from the longest slash-delimited prefix, so remote names that contain slashes are supported. Every other unresolvable ref is still rejected, and no fetch is attempted for a ref with no configured remote prefix.
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 Changed · +52 lines b0e5948eb7d3
- 13d ago First seen · 165 lines · 21 tokens per session scan A 6aa352b326de
roborev-review-branch is a skill published in the GitHub repository kenn-io/roborev (1,708 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 2,095 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to roborev-design-review-branch, differing in 109 lines, and is treated as a copy.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
oss-maintainer
Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.