review

review is a skill for Claude Code, Codex from vercel/eve. It costs 31 tokens per session (281 once invoked), scanned A, original, Apache-2.0.

A security and correctness audit of changed code, such as a branch or pull request. A pull request is a proposed code change reviewed before it is merged.

In plain words
What is it for?
It helps inspect changed code and related context, trace effects across packages and runtime systems, check authorization and untrusted input, and report only issues introduced or exposed by the change.
Why use it?
It looks for bugs, security weaknesses, broken behavior, setup problems, and accidental exposure of restricted features, while requiring evidence for each finding.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit It helps inspect changed code and related context, trace effects across packages and runtime systems, check authorization and untrusted input, and report only issues introduced or exposed by the change.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vercel/eve/review
About the project

eve is a filesystem-first framework for building durable AI agents, with agent instructions, tools, and configuration kept in ordinary project files. It is for developers creating agents that can be inspected, extended, and operated through a conventional codebase. The catalogue add-ons support working with eve agents and their workflows.

vercel/eve · 5,573 stars · on GitHub · eve.dev

Install

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.

Any agent
npx skills add vercel/eve --skill review
Clone the repo
git clone --depth 1 https://github.com/vercel/eve

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for review

README.md
[![agentmods](https://agentmods.dev/badge/skills/vercel/eve/review/github.svg)](https://agentmods.dev/skills/vercel/eve/review)
Your own site
<a href="https://agentmods.dev/skills/vercel/eve/review"><img src="https://agentmods.dev/badge/skills/vercel/eve/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.

agentmods 80×15 button for review

Your own site · 80×15
<a href="https://agentmods.dev/skills/vercel/eve/review"><img src="https://agentmods.dev/badge/skills/vercel/eve/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 281 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00281
Opus 5.5 $0.00012 $0.00112
Sonnet 5.5 $0.00006 $0.00056
Haiku 4.5 $0.00003 $0.00028

Measured 22d ago against content hash 7b813e407e01, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 22d 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.

packages/eve-code/extension/skills/review/SKILL.md · 22 lines

What it actually says

Deep review

Give the worker subagent a self-contained audit instruction naming the repository and target ref or worktree. The worker inspects the shared checkout directly. The root agent evaluates findings and owns the final verdict.

Audit changed code and its necessary surrounding context for bugs, broken functionality, security vulnerabilities, developer-experience regressions, and feature-gate leaks. Cite repository evidence for every finding. Report only issues introduced or exposed by code added or modified in the reviewed change.

Required checks

  • Trace cross-package and runtime side effects end to end.
  • Check authorization, untrusted input, credential disclosure, destructive behavior, and bounded work.
  • Check local build and run workflows, changed environment variables, ports, networking, and required setup.
  • Verify internal or gated features remain gated.
  • Distinguish intended, well-contained breakage from accidental consequences.
  • Calibrate priority carefully; do not inflate speculative or low-impact concerns.

Never present a finding with unfinished evidence. Name the exact missing file or ref instead. Run the independent audit before reading PR discussion so existing comments do not anchor it. Afterward, the root agent may compare findings with discussion, verify each against the workspace, and report only actionable defects.

Changes

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.

  1. 22d ago First seen · 22 lines · 31 tokens per session scan A 7b813e407e01

Subscribe to this mod's changes

review is a skill published in the GitHub repository vercel/eve (5,573 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 281 once invoked, about $0.0001 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-09-24.

Related

Other skills, from other repositories

triage-contributor-pr

Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…

prisma/orm · 131 tokens

open-code-review

Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…

alibaba/open-code-review · 98 tokens

open-code-review-delegate

Delegation mode for open-code-review (OCR). Instead of OCR calling an LLM endpoint, this skill instructs the host agent to perform the code review itself, using OCR only for deterministic engineering: file selection and rule resolution. Use when the host agent should drive the review with its own LLM capabilities.

alibaba/open-code-review · 68 tokens

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.

prisma/orm · 38 tokens

review-triage-phase

Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.

prisma/orm · 36 tokens

no-bare-casts

Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.

prisma/orm · 52 tokens