review

review is a command for Claude Code from Pharaoh-so/pharaoh-mcp. It costs 6 tokens per session (4,927 once invoked), scanned A, original, MIT.

A structured code-review command that checks a branch's changes against the surrounding code and architecture. It uses several reviewers and returns a verdict of SHIP, SHIP WITH CHANGES, or BLOCK.

In plain words
What is it for?
Use it before merging a branch or opening a pull request (a request to merge code changes). It reviews implementation claims, exported functions, core data flows, and changes against a specification.
Why use it?
It helps find problems that a file-by-file review can miss, especially when changes affect shared modules or data flows. It also checks exactly which branch and commits are being reviewed.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

Part of the pharaoh plugin — 8 skills, 2 commands, 1 hook, 1 MCP server shipped together

Good fit Use it before merging a branch or opening a pull request (a request to merge code changes). It reviews implementation claims, exported functions, core data flows, and changes against a specification.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/pharaoh-so/pharaoh-mcp/review
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.

Clone the repo
git clone --depth 1 https://github.com/Pharaoh-so/pharaoh-mcp

Made for: Claude Code.

Or install pharaoh, the plugin that ships this one along with the rest of its 8 skills, 2 commands, 1 hook, 1 MCP server.

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/pharaoh-so/pharaoh-mcp/review/github.svg)](https://agentmods.dev/commands/pharaoh-so/pharaoh-mcp/review)
Your own site
<a href="https://agentmods.dev/commands/pharaoh-so/pharaoh-mcp/review"><img src="https://agentmods.dev/badge/commands/pharaoh-so/pharaoh-mcp/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/pharaoh-so/pharaoh-mcp/review"><img src="https://agentmods.dev/badge/commands/pharaoh-so/pharaoh-mcp/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6 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,927 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.00006 $0.04927
Opus 5.5 $0.00002 $0.01971
Sonnet 5.5 $0.00001 $0.00985
Haiku 4.5 $0.00001 $0.00493

Measured yesterday against content hash c2d73bd85e10, 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 yesterday.

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.

commands/review.md · 353 lines

How it starts

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

Review with Pharaoh

The definitive code review, for any codebase. Architecture-aware, branch-aware, multi-agent, adversarial. Five phases that combine Pharaoh's knowledge graph with parallel specialized reviewers and an independent second opinion from a different model. Every phase works without Pharaoh too; Pharaoh makes the architecture picture exact and cheap where it maps the repo.

A review always reaches a verdict. When a phase needs something your client doesn't have (Pharaoh, a shell, subagents, a second model), it says how to carry on without it: do that, and name what was missing in the review output. Ask the user only when someone is there to answer.

Final verdict: SHIP / SHIP WITH CHANGES / BLOCK

When to Use

Before merging any branch. Before opening any PR. When reviewing changes that touch shared modules, export new functions, modify core data flows, or claim to implement a spec.


Phase 0 — Git Context

Goal: Know exactly what changed and where you are. This phase is mandatory and runs before anything else.

No shell, or no git? Review the diff you were given (a file, a pasted patch, a pull request's changes): take the changed files and touched modules from it, skip to step 5, and say in the review output that branch context wasn't available.

  1. Detect the current environment:

    git rev-parse --show-toplevel          # repo root (may be a worktree)
    git worktree list                      # detect if running in a worktree
    git branch --show-current              # current branch name
    git log --oneline -1                   # latest commit
    
  2. Determine the base (where this branch diverged from the branch it merges into). The target is the first of these that resolves:

    TARGET=$(gh pr view --json baseRefName --jq '"origin/" + .baseRefName' 2>/dev/null)   # the open PR's target branch
    [ -n "$TARGET" ] || TARGET=$(git symbolic-ref -q --short refs/remotes/origin/HEAD)    # the default branch, set by git clone
    [ -n "$TARGET" ] || for b in origin/main origin/master main master; do
      git rev-parse -q --verify "$b" >/dev/null && TARGET=$b && break
    done
    BASE=$(git merge-base HEAD "$TARGET") && echo "base: $BASE"
    

    If no base comes out, ask which branch this merges into (with no one to ask, review the uncommitted changes from step 4 and say the base was unknown). An empty base makes every diff below come out empty, and the review would report no changes. If your shell doesn't keep variables between commands, set BASE to the printed commit at the start of each one.

Read the full file on GitHub · 353 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. yesterday Changed · +55 lines c2d73bd85e10
  2. 4d ago First seen · 298 lines · 6 tokens per session scan A f011c1d759a8

Subscribe to this mod's changes

review is a command published in the GitHub repository Pharaoh-so/pharaoh-mcp (2 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 4,927 once invoked, about $0.0000 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-10-21.