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.
npx agentmods add commands/mturac/everything-openai-codex/review-prgit clone --depth 1 https://github.com/mturac/everything-openai-codexWrote 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/mturac/everything-openai-codex/review-pr)<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/review-pr"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/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.00257 |
| Opus 5 | $0.00003 | $0.00129 |
| Sonnet 5 | $0.00001 | $0.00051 |
| 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 3d 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.
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
CODEX.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.
- 3d ago First seen · 38 lines · 7 tokens per session scan A 67784a4c8ede
review-pr is a command published in the GitHub repository mturac/everything-openai-codex (89 stars, last pushed 13d ago), licensed MIT. It adds 7 tokens to every session and 257 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
refactor-sprint
Parallel refactor sprint — fires refactor-cleaner + code-simplifier + type-design-analyzer + tdd-guide simultaneously. Full cleanup in one pass.
validate-parallel
Run assert and review-code commands in parallel to reduce validation time by 50%.
orch-refine-code
Orchestrate a behavior-preserving refactor — confirm tests green, restructure without changing behavior, keep green, review, gated commit. Wrapper for the orch-refine-code skill.
qa
Use when performing local QA review before pushing PR changes. Evaluates test coverage, error handling, and code quality.
code-permutation-tester
Test multiple code variations through simulation before implementation with quality gates and performance prediction.
checklist
Generate a custom checklist for the current feature based on user requirements.