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-lookahead-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-lookahead-review-branch)<a href="https://agentmods.dev/skills/kenn-io/roborev/roborev-lookahead-review-branch"><img src="https://agentmods.dev/badge/skills/kenn-io/roborev/roborev-lookahead-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-lookahead-review-branch"><img src="https://agentmods.dev/badge/skills/kenn-io/roborev/roborev-lookahead-review-branch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 83 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00025 | $0.01579 |
| Opus 5 | $0.00013 | $0.00790 |
| Sonnet 5 | $0.00005 | $0.00316 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade A, and why
roborev-lookahead-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 12d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
roborev-lookahead-review-branch
Request a time-series look-ahead review for all commits on the current branch and present the results. A look-ahead review checks whether the change uses information that would not yet be available at the point in time it represents — also called peekahead, future leakage, or temporal leakage.
Usage
/roborev-lookahead-review-branch [--base <branch>] [--panel <name>|none]
Explicit invocation only
Invocation must be explicit: literal personal /roborev-lookahead-review-branch, or structured
Claude Code skill selection.
Requests such as “check this branch for future leakage” 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-lookahead-review-branch [--base <branch>] [--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.
If validation fails, inform the user the ref is invalid. Do not proceed.
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.
- 12d ago First seen · 167 lines · 25 tokens per session scan A faee635d0ec0
roborev-lookahead-review-branch is a skill published in the GitHub repository kenn-io/roborev (1,708 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 1,579 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
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.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…