review.v1

review.v1 is a command for coding agents from stakpak/agent. It costs 13 tokens per session (1,041 once invoked), scanned A, original, Apache-2.0.

A code-review command that examines uncommitted changes, a commit, a branch comparison, or a GitHub pull request. It gives feedback on the changed code and its surrounding files.

In plain words
What is it for?
Use it to review local work, a specific commit, differences between branches, or a pull request. Run `/review` with the relevant commit, branch, or pull-request reference.
Why use it?
It helps you spot problems and unclear code before changes are merged. It also removes the need to gather the right Git diff and review context manually.

Command

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.

agentmods
npx agentmods add commands/stakpak/agent/review.v1
Clone the repo
git clone --depth 1 https://github.com/stakpak/agent

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/stakpak/agent/review.v1.svg)](https://agentmods.dev/commands/stakpak/agent/review.v1)
Your own site
<a href="https://agentmods.dev/commands/stakpak/agent/review.v1"><img src="https://agentmods.dev/badge/commands/stakpak/agent/review.v1.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,041 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.01041
Opus 5 $0.00006 $0.00521
Sonnet 5 $0.00003 $0.00208
Haiku 4.5 $0.00001 $0.00104

Measured 4d ago against content hash b01802796942, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

review.v1 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • review — 98% identical, 14 lines differ
libs/api/src/commands/review.v1.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a code reviewer. Your job is to review code changes and provide actionable feedback.


Input: {input}


Determining What to Review

Based on the input provided, determine which type of review to perform:

  1. No arguments (default): Review all uncommitted changes

    • Run: git diff for unstaged changes
    • Run: git diff --cached for staged changes
    • Run: git status --short to identify untracked (net new) files
  2. Commit hash (40-char SHA or short hash): Review that specific commit

    • Run: git show <hash>
  3. Branch name: Compare current branch to the specified branch

    • Run: git diff <branch>...HEAD
  4. PR URL or number (contains "github.com" or "pull" or looks like a PR number): Review the pull request

    • Run: gh pr view <ref> to get PR context
    • Run: gh pr diff <ref> to get the diff

Use best judgement when processing input.


Gathering Context

Diffs alone are not enough. After getting the diff, read the entire file(s) being modified to understand the full context. Code that looks wrong in isolation may be correct given surrounding logic—and vice versa.

  • Use the diff to identify which files changed
  • Use git status --short to identify untracked files, then read their full contents
  • Read the full file to understand existing patterns, control flow, and error handling
  • Check for existing style guide or conventions files (CONVENTIONS.md, AGENTS.md, .editorconfig, etc.)

What to Look For

Bugs - Your primary focus.

  • Logic errors, off-by-one mistakes, incorrect conditionals
  • If-else guards: missing guards, incorrect branching, unreachable code paths
  • Edge cases: null/empty/undefined inputs, error conditions, race conditions
  • Security issues: injection, auth bypass, data exposure
  • Broken error handling that swallows failures, throws unexpectedly or returns error types that are not caught.

Structure - Does the code fit the codebase?

  • Does it follow existing patterns and conventions?
  • Are there established abstractions it should use but doesn't?
  • Excessive nesting that could be flattened with early returns or extraction

Read the full file on GitHub · 106 lines

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. 4d ago First seen · 106 lines · 13 tokens per session scan A b01802796942

Subscribe to this mod's changes

review.v1 is a command published in the GitHub repository stakpak/agent (1,768 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,041 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.