Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. 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/egregore-labs/egregore/main/.claude/skills/review-pr/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/skills/egregore-labs/egregore/review-pr)<a href="https://agentmods.dev/skills/egregore-labs/egregore/review-pr"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/review-pr/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/skills/egregore-labs/egregore/review-pr"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/review-pr.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.00056 | $0.03372 |
| Opus 5.5 | $0.00022 | $0.01349 |
| Sonnet 5.5 | $0.00011 | $0.00674 |
| Haiku 4.5 | $0.00006 | $0.00337 |
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 24d 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review a pull request with CTO-level scrutiny. Designed for vibe-coded PRs.
Arguments: $ARGUMENTS
When to invoke
User says: "review PR", "check this PR", "review #123", "is this PR safe to merge", "audit PR", "review cem's PRs" Not this: "/pr" (create a PR), "/test" (validate local changes)
Execution rules
CRITICAL: Suppress raw output. Never show raw JSON, raw diffs, or unformatted gh output. All output should be structured assessment.
For diff review, delegate to a subagent when available and permitted in this session; otherwise do it inline. When delegation is available and permitted in this session, each PR gets its own background subagent for parallel analysis. In either case, fetch the diff, analyze it, and return a structured verdict.
Auth: Run every gh command through bash bin/gh-run.sh; the helper reads and trims GITHUB_TOKEN from the project's .env and passes it directly to the child environment when nonempty, otherwise preserving the existing login. Never read, print, or type the secret.
Step 0: Determine scope
Parse $ARGUMENTS:
- PR number (e.g.
123,#123) → review that single PR - Author (e.g.
alice,bob) → list all open PRs from that author --all→ list all open PRs- Empty → list all open PRs targeting develop
Get org/repo:
bash bin/config-get.sh github_org
Read the configured repository name:
bash bin/config-get.sh repo_name
Use each printed value as {github_org} or {repo_name} below; quote it in single quotes when you use it in a command, and write any single quote inside the value as '\''.
Step 1: Fetch PR metadata
Single PR
Use {pr_number} from the command's arguments or the selected PR metadata, and {github_org} and {repo_name} from configuration:
bash bin/gh-run.sh pr view '{pr_number}' --json title,author,additions,deletions,changedFiles,headRefName,body,createdAt,state --repo '{github_org}/{repo_name}'
Multiple PRs (author or --all)
Use {github_org} and {repo_name} from configuration with the credential helper:
bash bin/gh-run.sh pr list --state open --json number,title,author,additions,deletions,changedFiles,headRefName,createdAt --limit 50 --repo '{github_org}/{repo_name}'
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.
- 24d ago Changed · +27 lines 760a380e5e78
- 1mo ago First seen · 277 lines · 56 tokens per session scan A 79e34af58e74
review-pr is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 56 tokens to every session and 3,372 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
handoff-protocols
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or…
parallel-investigation
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist…
structured-code-review
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR…
bothread
Join and behave correctly in a Bothread room — a shared, human-governed space where you collaborate with other AI agents on one codebase. Use this when the user says they want you to join a Bothread session, gives you a Bothread session ID, or asks you to coordinate with other agents.
git-workflow
Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.
mflow
Use when working in a repo that uses mflow, coordinating multiple AI agents/worktrees, setting up mflow sync, installing mflow MCP in Codex/Claude Code/Cursor/opencode, or before git operations where synced file changes may affect commits. Applies to CLI, MCP, room secrets, pause/resume, locks, status checks, and safe…