edgar-mcp: Command for Claude Code

.claude/commands/review-pr.md

review-pr is a command for Claude Code from mcpwright/edgar-mcp. It costs 26 tokens per session (308 once invoked), scanned A, original, MIT.

A command that asks a separate code-review agent to inspect the current branch’s changes before a pull request. A pull request is a request to merge code into another branch.

In plain words
What is it for?
It is for comparing a branch with a base such as main, launching a fresh-context review, and reporting findings without fixing them automatically.
Why use it?
It provides an independent review of the actual diff and prevents opening a pull request before checking for problems.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents; positional $N argument.

This is mcpwright/edgar-mcp's own configuration. It tells Claude Code how to work on edgar-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything edgar-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mcpwright/edgar-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mcpwright/edgar-mcp/main/.claude/commands/review-pr.md
Clone the repo
git clone --depth 1 https://github.com/mcpwright/edgar-mcp

Made for: Claude Code.

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-pr

README.md
[![agentmods](https://agentmods.dev/badge/commands/mcpwright/edgar-mcp/review-pr.svg)](https://agentmods.dev/commands/mcpwright/edgar-mcp/review-pr)
Your own site
<a href="https://agentmods.dev/commands/mcpwright/edgar-mcp/review-pr"><img src="https://agentmods.dev/badge/commands/mcpwright/edgar-mcp/review-pr.svg" alt="Measured on agentmods" 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 308 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.1 $0.00026 $0.00308
Opus 5 $0.00013 $0.00154
Sonnet 5 $0.00005 $0.00062
Haiku 4.5 $0.00003 $0.00031

Measured 5d ago against content hash ce71cfc3cf0a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

review-pr 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 5d 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

4 near-identical copies found in the catalogue:

.claude/commands/review-pr.md · 22 lines

What it actually says

Run a pre-PR code review of the current branch using the code-reviewer subagent. The point is a review in a fresh context — so do not summarize the diff yourself; let the subagent read the code.

Base ref: $1 (default main if empty).

  1. Sanity-check the range: run git log <base>..HEAD --oneline and git diff --stat <base>...HEAD so you (and I) can see what's in scope. If the branch is main or has no commits over the base, stop and say so.
  2. Launch the code-reviewer subagent (Task tool, subagent_type: code-reviewer). Tell it only the base ref and that it should run git diff <base>...HEAD and read the touched files itself. Do not paste the diff or describe the change — its value is the independent read.
  3. Relay the subagent's report back verbatim under a ## Code review heading.
  4. Do not fix anything yet. Wait for me to decide which findings to address; then I'll have you fold them in before the PR.
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. 5d ago First seen · 22 lines · 26 tokens per session scan A ce71cfc3cf0a

Subscribe to this mod's changes

review-pr is a command published in the GitHub repository mcpwright/edgar-mcp (1 stars, last pushed 16d ago), licensed MIT. It adds 26 tokens to every session and 308 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-31.