Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yonatangross/orchestkitnpx agentmods add commands/yonatangross/orchestkit/review-prWrote 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/yonatangross/orchestkit/review-pr)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/review-pr"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/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/commands/yonatangross/orchestkit/review-pr"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/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.00069 | $0.08980 |
| Opus 5.5 | $0.00028 | $0.03592 |
| Sonnet 5.5 | $0.00014 | $0.01796 |
| Haiku 4.5 | $0.00007 | $0.00898 |
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.
How it starts
The opening of the file, as written. The whole thing — 462 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/review-pr/SKILL.md
Source: https://github.com/yonatangross/orchestkit
Review PR
Host-neutral workflow. Invoke by skill name (review-pr). Claude Code slash routing, YAML hook loaders, and .claude/chain live in skills/review-pr/references/claude-code.md.
Deep code review using 6-7 parallel specialized agents.
Quick Start
review-pr 123
review-pr feature-branch
Opus 5.5: Parallel agents use native adaptive thinking for deeper analysis. Complexity-aware routing matches agent model to review difficulty.
Argument Resolution
A pronoun target (this, them, the above) is read back from the conversation, announced in one line, and used: Read("../../shared/rules/target-resolution.md"), inline half.
Resolve the target with the script first, then review exactly that target (#3892). Read the mode and opt-in flags (--rules, --standards, --post, --post-verdict) from the arguments yourself and drop them, then run the script as one plain command (the post gate allows only simple read-only commands, so no assignment, loop or $(...)):
bash skills/review-pr/scripts/resolve-target.sh <the arguments without the four flags> # prints one JSON object: TARGET
kind |
Comes from | Review source |
|---|---|---|
pr |
123, #123, a PR URL, ORCHESTKIT_PR_URL, or the current branch's open PR (no argument) |
PR_NUMBER; the gh pr view/diff/checks commands below |
range |
base...head or base..head, e.g. origin/main...origin/qa |
git diff base...head, git log base..head; skip gh pr checks and Phase 6 submit |
ref |
a branch or ref that resolves | gh pr view <ref>: open PR, treat as pr; none, review <default>...<ref> as range |
ask |
anything else, or no argument and no PR | STOP and AskUserQuestion for a PR number or ref range |
Never substitute HEAD, the current checkout, or its branch for a target the user did not name. On ask, stop and ask. State the resolved target in your first line of output, and use PR_NUMBER (or the range) consistently in every later command and agent prompt.
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 Changed · +2 lines 936b4ef61b1b
- 9d ago Changed · +2 lines 73be69292c9f
- 10d ago Changed · +4 lines 758f35595c81
- 11d ago Changed · -2 lines ce877d147835
- 12d ago Changed · +2 lines 10b0306525c7
- 19d ago Changed · +15 lines 92df064a4373
- 21d ago Changed f90c6b46dfc6
- 23d ago Changed · -31 lines 0f9ed628a49e
- 25d ago Changed · +2 lines 9a8d7d817ee8
- 27d ago First seen · 468 lines · 69 tokens per session scan A a62eba635173
review-pr is a command published in the GitHub repository yonatangross/orchestkit (298 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 8,980 once invoked, about $0.0003 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 commands, from other repositories
gc
On-demand code-drift / entropy scan (garbage collection) via a fresh-context drift-analyst subagent. Checks changed/active code against golden-rules.md + generic drift heuristics (dead code, duplication, doc-drift) and reports findings with an evidence path. Read-only — recommends, never auto-refactors. Not git gc.
pn-audit-api
Surgical API design review — REST conventions, status codes, response shapes, validation, and schema leaks. Use standalone or as part of pn-backend-audit. Outputs a scored fix roadmap.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.