Borrowing it
Nothing to install: this file belongs to Parslee-ai/neo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Parslee-ai/neo/main/.claude/commands/pr-review.mdgit clone --depth 1 https://github.com/Parslee-ai/neoWrote 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.
[](https://agentmods.dev/commands/parslee-ai/neo/pr-review)<a href="https://agentmods.dev/commands/parslee-ai/neo/pr-review"><img src="https://agentmods.dev/badge/commands/parslee-ai/neo/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.
<a href="https://agentmods.dev/commands/parslee-ai/neo/pr-review"><img src="https://agentmods.dev/badge/commands/parslee-ai/neo/pr-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00047 | $0.01428 |
| Opus 5 | $0.00023 | $0.00714 |
| Sonnet 5 | $0.00009 | $0.00286 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
pr-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.
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review
Review a GitHub pull request for bugs, security issues, and code quality with complete context awareness.
Variables
PR_URL: $1 BASE_BRANCH: $2 DESCRIPTION: $3
Workflow
Step 1: Use @sentinel to Fetch PR Context
Fetch complete PR context using the gh CLI:
- PR Metadata: Run
gh pr view $PR_URL --json body,title,author,labels,baseRefName,number - PR Review Comments: Run
gh api repos/{owner}/{repo}/pulls/{number}/comments - Review Threads: Run
gh api repos/{owner}/{repo}/pulls/{number}/reviews - Issue Comments: Run
gh api repos/{owner}/{repo}/issues/{number}/comments(conversation tab)
Extract the following critical information:
baseRefName- This is the base branch for the PRauthor.login- This is the PR author's GitHub username
Format the output as a comprehensive PR Context document that includes:
- Title: The PR title
- Author: @mention format (e.g., @username)
- Base Branch: The branch this PR targets
- Labels: Any labels applied to the PR
- PR Description: The full body of the PR
- Conversation & Comments: All comments from all sources, organized chronologically
This context will be passed to the code reviewer in Step 2.
Step 2: Use @brutal-reviewer to Perform Code Review
Pass the following information to @brutal-reviewer:
Input:
- PR URL: $PR_URL
- Base Branch: Use $BASE_BRANCH if provided by user, otherwise use the baseRefName from Step 1
- User-Provided Context: Use $DESCRIPTION if provided by user, otherwise "None provided"
- Full PR Context: The complete context document from Step 1
Instructions for brutal-reviewer:
Review this GitHub pull request with full context:
PR URL: [PR_URL from above] Base Branch: [BASE_BRANCH from above] User Context: [DESCRIPTION from above] Full PR Context: [Complete context from Step 1]
Your Task:
- Checkout the PR using gh CLI or git fetch
- Generate diff against base branch using git merge-base to find common ancestor
- Review ONLY the changed lines (lines with '+' prefix in the diff)
- Use the PR description and conversation context to understand the intent and context
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.
- 10d ago First seen · 173 lines · 47 tokens per session scan A aaf5e73c008a
pr-review is a command published in the GitHub repository Parslee-ai/neo (16 stars, last pushed 2d ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,428 once invoked, about $0.0002 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.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.