review

review is a command for Claude Code from TOMOSIA-VIETNAM/open-pr. It costs 26 tokens per session (4,633 once invoked), scanned A, original, MIT.

A command for reviewing pull requests against conventions learned from each repository. It leaves the reviewed code unchanged and publishes review findings in a single review post.

In plain words
What is it for?
Use it to inspect a GitHub pull request or GitLab merge request, identify issues by severity, and report them without modifying the repository.
Why use it?
It keeps code review focused and consistent while preventing the reviewer from editing, merging, or otherwise changing the proposed work.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the open-pr plugin — 5 commands shipped together

Good fit Use it to inspect a GitHub pull request or GitLab merge request, identify issues by severity, and report them without modifying the repository.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add TOMOSIA-VIETNAM/open-pr
Claude Code
/plugin install open-pr

Made for: Claude Code.

Or install open-pr, the plugin that ships this one along with the rest of its 5 commands.

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/commands/tomosia-vietnam/open-pr/review/github.svg)](https://agentmods.dev/commands/tomosia-vietnam/open-pr/review)
Your own site
<a href="https://agentmods.dev/commands/tomosia-vietnam/open-pr/review"><img src="https://agentmods.dev/badge/commands/tomosia-vietnam/open-pr/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/commands/tomosia-vietnam/open-pr/review"><img src="https://agentmods.dev/badge/commands/tomosia-vietnam/open-pr/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,633 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.00026 $0.04633
Opus 5 $0.00013 $0.02316
Sonnet 5 $0.00005 $0.00927
Haiku 4.5 $0.00003 $0.00463

Measured 10d ago against content hash 074bc47b4fa6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 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.

src/commands/review.md · 316 lines

How it starts

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

CRITICAL: Read "${CLAUDE_PLUGIN_ROOT}"/core/guardrails.md FIRST — shared rules, not repeated here. On top of those:

  • Read-only on the reviewed repo; the only write is Step 9's 1 review (+ 1 more on a submodule PR when Step 1 detects a bump). FORBIDDEN: close/merge/reopen, create/delete/switch a branch, push, edit code → mention it in the review instead.
  • git worktree add confined to notebooks/review/*/worktrees/*.
  • Read/Grep in the worktree may surface the REVIEWED repo's own .claude/skills/ — its dev workflow, not a review tool. FORBIDDEN: invoking it, even when listed as available.

Step 0 — Target

Read "${CLAUDE_PLUGIN_ROOT}"/core/pr-target.md; it names what every later Step reuses. Usage: block for this command:

❌ Error: No PR URL provided.
Usage: /open-pr:review <PR URL>
Example (GitHub): /open-pr:review https://github.com/org/repo/pull/123
Example (GitLab): /open-pr:review https://gitlab.com/org/repo/-/merge_requests/123

A language instruction in ARGUMENTS/chat overrides .shared.output_language, this run only.

≥2 valid PR URLs && the intent isn't already clear from ARGUMENTS/chat → ask "Found N PRs — review all N or just the first?", WAIT (extras may be reference-only). Confirmed multi-PR → run Step 0 → Step 9 to COMPLETION per URL, in order, SEQUENTIALLY, each with its own worktree/memory/post. FORBIDDEN: parallel, subagent. [content] applies to every PR. All done → 1 chat summary, 1 line per PR, shaped by Step 9's reporting rule; nothing further posted.

Context

<git_remote_type> MUST be resolved (core/pr-target.md §2) BEFORE the first fetch, which needs .shared.git_remote_type → try Reading notebooks/review/<repo>/settings.json now (Step 3 re-Reads it for the rest of its content).

Then fetch:

entry label
"Fetch PR basic info", fields number,title,body,author,baseRefName,headRefName PR info
"Fetch PR head commit SHA" Head SHA
"Fetch PR diff — file list" Files
"Fetch PR diff size per file" Diff size per file
"Fetch PR diff — patch, omitting oversized files", <max_patch_bytes> = big_file_threshold_kb × 1024 Diff
"Fetch PR commits headlines" Commits
"Fetch PR review comments (LINE-level findings)" Old comments
"Fetch CI checks" CI checks

Read the full file on GitHub · 316 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. 10d ago First seen · 316 lines · 26 tokens per session scan A 074bc47b4fa6

Subscribe to this mod's changes

review is a command published in the GitHub repository TOMOSIA-VIETNAM/open-pr (42 stars, last pushed 5d ago), licensed MIT. It adds 26 tokens to every session and 4,633 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.