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.
git clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/fmarzochi/egc/review-pr)<a href="https://agentmods.dev/commands/fmarzochi/egc/review-pr"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/review-pr.svg" alt="Measured on agentmods" 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.00007 | $0.00258 |
| Opus 5 | $0.00003 | $0.00129 |
| Sonnet 5 | $0.00001 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
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 4d 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.
This is a copy
91% identical to review-pr — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Run a comprehensive multi-perspective review of a pull request.
Usage
/review-pr [PR-number-or-URL] [--focus=comments|tests|errors|types|code|simplify]
If no PR is specified, review the current branch's PR. If no focus is specified, run the full review stack.
Steps
- Identify the PR:
- use
gh pr viewto get PR details, changed files, and diff
- use
- Find project guidance:
- look for
GEMINI.md, lint config, TypeScript config, repo conventions
- look for
- Run specialized review agents:
code-reviewercomment-analyzerpr-test-analyzersilent-failure-huntertype-design-analyzercode-simplifier
- Aggregate results:
- dedupe overlapping findings
- rank by severity
- Report findings grouped by severity
Confidence Rule
Only report issues with confidence >= 80:
- Critical: bugs, security, data loss
- Important: missing tests, quality problems, style violations
- Advisory: suggestions only when explicitly requested
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.
- 4d ago First seen · 38 lines · 7 tokens per session scan A a22688c301b3
review-pr is a command published in the GitHub repository Fmarzochi/EGC (49 stars, last pushed today), licensed Apache-2.0. It adds 7 tokens to every session and 258 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to review-pr, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
thermo-nuclear-code-quality-review
Extremely strict maintainability review hunting for code-judo simplifications, giant files, and spaghetti-condition growth.
start
Read and follow the skill at .cursor/skills/start/SKILL.md.
review
A command that reviews code changes across correctness, readability, architecture, security, and performance.
review-code
Perform comprehensive code quality review including standards, security, maintainability, and best practices validation.
pr-review
Review a GitHub pull request: analyzes changed files to select relevant reviewers, loads project and user memory, runs reviewers in parallel, lets the user pick which findings to post, then submits the review on behalf of the user via gh CLI.
code-simplify
Simplify code for clarity and maintainability — reduce complexity without changing behavior.