A read-only second review of the current Git changes, optionally including Codex's own reviewer. Git is a tool that records code changes, and the review can cover uncommitted work or changes since a chosen branch.

Use it to inspect staged, unstaged, and untracked files, or to review the difference between a branch and the current code. Add `codex` for an additional native review.

It provides another check for mistakes before code is accepted. It also makes it clear exactly which local or branch changes are being reviewed.

pair-review — Skill for Claude Code and Codex by hyj28

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 hyj28/claude-codex-pair --skill pair-review

Clone the repo

git clone --depth 1 https://github.com/hyj28/claude-codex-pair

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hyj28/claude-codex-pair/pair-review/github.svg)](https://agentmods.dev/skills/hyj28/claude-codex-pair/pair-review)

Your own site

<a href="https://agentmods.dev/skills/hyj28/claude-codex-pair/pair-review"><img src="https://agentmods.dev/badge/skills/hyj28/claude-codex-pair/pair-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hyj28/claude-codex-pair/pair-review"><img src="https://agentmods.dev/badge/skills/hyj28/claude-codex-pair/pair-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 547 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.00547
Opus 5.5	$0.00016	$0.00219
Sonnet 5.5	$0.00008	$0.00109
Haiku 4.5	$0.00004	$0.00055

Measured 1mo ago against content hash fb0a9fb1520c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

pair-review scanned grade B with 1 finding 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 1mo 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

not be inherited from `~/.codex/config.toml`, which may be temporarily set to a laxer mode.

skills/pair-review/SKILL.md · 40 lines

How it starts

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

/pair-review — quick second pair of eyes on current changes

Lightweight standalone review, for when the full /pair workflow is not in play (e.g. the user or Codex wrote code directly and just wants it checked).

Arguments

/pair-review [codex] [base <branch>]

No args: review uncommitted changes (staged + unstaged + untracked) with a fresh Claude subagent.
base <branch>: review git diff <branch>...HEAD instead of uncommitted changes.
codex: ALSO run Codex's native reviewer and merge findings:
- uncommitted scope: codex exec -s read-only -c approval_policy=never review --uncommitted
- base scope: codex exec -s read-only -c approval_policy=never review --base <branch>
Pass -s read-only explicitly — reviewing never needs write access, and the sandbox must not be inherited from ~/.codex/config.toml, which may be temporarily set to a laxer mode.

Procedure

Confirm there is actually something to review (git status --porcelain / the diff is non-empty). If empty, say so and stop.
Spawn a fresh-context subagent as the reviewer. It must be read-only (Read/Grep/Glob/read-only Bash; never edit). Give it the diff scope and instruct: report only real defects, each with file:line, a one-sentence claim, and a concrete failure scenario (inputs/state → wrong behavior). No style nits, no speculation. Judge the tests too, and treat a bad test as a defect: a test whose expected value is recomputed the way the code computes it, one that passes only because a collaborator was mocked out, one coupled to internals rather than a public boundary, or a diff that deletes or loosens assertions in the existing suite. Note behavior the diff adds with no test.
If codex was requested, run the codex review command in parallel with a generous timeout.
Merge and dedupe findings, ranked most severe first. Note which reviewer found what only when the two disagree.
Report the findings to the user. Do not fix anything unless the user then asks.

Read the full file on GitHub · 40 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.

1mo ago First seen · 40 lines · 40 tokens per session scan B fb0a9fb1520c

Subscribe to this mod's changes

pair-review is a skill published in the GitHub repository hyj28/claude-codex-pair (4 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 547 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Code review Git and workflow agentic-workflow ai-agents anthropic cli

pull-request

How to run a pull request to the point where it can be merged — resolving every review conversation, checking every workflow run rather than the summary, and confirming the merge result is what CI actually tested. Load this whenever you open, update, review, or merge a PR, whenever a review round returns findings, and…

olehsvyrydov/AI-development-team · 78 tokens

ship-pr

Run the project checks and open a pull request once they pass.

zernie/vigiles · 15 tokens

diffctx

Use when reviewing or explaining a commit, PR, branch or uncommitted diff — "review my last commit", "review before merge", "review my changes", "what else does this change affect" — the callers and tests the change reaches outside its diff, then the surrounding code.

nikolay-e/diffctx · 57 tokens

pair-review