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 skills/morpho-org/sdks/pr-review-enginenpx skills add morpho-org/sdks --skill pr-review-enginegit clone --depth 1 https://github.com/morpho-org/sdksWrote 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/morpho-org/sdks/pr-review-engine)<a href="https://agentmods.dev/skills/morpho-org/sdks/pr-review-engine"><img src="https://agentmods.dev/badge/skills/morpho-org/sdks/pr-review-engine.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 | $0.00063 | $0.07955 |
| Opus 5 | $0.00032 | $0.03978 |
| Sonnet 5 | $0.00013 | $0.01591 |
| Haiku 4.5 | $0.00006 | $0.00796 |
Grade A, and why
pr-review-engine 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 today.
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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-review-engine — shared multi-lens review dispatcher
This file is the shared review engine for the /pr-review-ci, /pr-review-gh, /pr-review-local, and /pr-fix slash commands. It supersedes the previous shared dispatcher at .agents/lib/pr-review-base.md.
Do NOT invoke this file directly. It is consumed by other commands — it is not symlinked into .claude/commands/ and assumes the caller has resolved branches and head SHA in its own Steps 1–2. Callers hand control to this file's Steps 3–6.
The base contract: callers pass these resolved values into Steps 3–6 and consume the deduplicated findings list + <FAILED_AGENTS> count produced by Step 6.
Runtime requirement. The bundled scripts under
scripts/are run asnode .agents/pr-review-engine/scripts/<file>.tsand rely on Node's native TypeScript type-stripping (Node ≥ 22.18; the repo's dev/CI runtime is newer). This is a requirement of the review tooling only — it is not the published-package Node floor (engines.nodein the rootpackage.json).
Success criteria
How a caller knows the engine is working (rough targets, not hard thresholds):
- Triggering precision — CI/release-only diffs fire
ci-release-security; protocol-surface diffs collect ABI/address context formorpho-protocolandweb3-security; agentic-system diffs fireskill-authoring. - False-positive ceiling — ≤ 10% of agent findings dropped by the scope filter on a healthy diff. If consistently higher, the diff path normalization or
<CHANGED_LINES>build is wrong. - 0 failed agents on a clean diff —
<FAILED_AGENTS>is empty when every agent's JSON parses and matches the WHAT/FIX schema. If non-zero, check schema injection in Step 5. - Bounded cost — a typical review fans out 8 baseline + 0–2 conditional agents.
Inputs (from caller's Steps 1–2)
| Caller-provided | Source |
|---|---|
<OWNER>, <REPO> |
parsed from git remote |
<HEAD_BRANCH> |
gh pr view → headRefName (PR modes) OR git branch --show-current (Local-only) |
<BASE_BRANCH> |
gh pr view → baseRefName (PR modes) OR --local arg / auto-detected default branch |
<HEAD_SHA> |
gh pr view → headRefOid (PR modes) OR git rev-parse HEAD (Local-only) |
<DIFF_SOURCE> |
pr (use origin/<BASE_BRANCH>...<HEAD_REF>) OR local (use origin/<BASE_BRANCH>...HEAD and overlay uncommitted) |
<HEAD_REF> |
Caller-supplied for <DIFF_SOURCE>=pr (origin/<HEAD_BRANCH>, or origin/pr/<PR_NUMBER> when fetched via refs/pull/<PR_NUMBER>/head — required for fork PRs); HEAD for <DIFF_SOURCE>=local |
<EXCLUDE_AGENTS> |
Optional list of agent names to skip in Step 5 (e.g. ["documentation"] from /pr-review-local --fast). Defaults to empty. |
<INTENT_CONTEXT> |
Optional caller-supplied intent/history block — changed-commit messages, and (when the caller talks to GitHub) the PR title+body. Injected into the Step 5 envelope between items 6 and 7. Empty by default; callers that can't reach the data omit it. |
What ships with it
27 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/ci-release-security.md 11 KB
- agents/code-quality.md 4.7 KB
- agents/documentation.md 8.5 KB
- agents/module-api-architecture.md 6.2 KB
- agents/morpho-protocol.md 6.8 KB
- agents/silent-failure-hunter.md 3.4 KB
- agents/skill-authoring.md 6.6 KB
- agents/style-conventions.md 4.0 KB
- agents/test-coverage.md 4.8 KB
- agents/web3-security.md 8.5 KB
- references/calibration.md 1.8 KB
- references/changed-lines.md 2.7 KB
- references/github-actions.md 5.3 KB
- references/injection.md 3.2 KB
- references/scope-filter.md 2.9 KB
- references/secrets.md 2.9 KB
- references/skill-authoring.md 5.4 KB
- scripts/build-changed-lines.test.ts 9.5 KB runs code
- scripts/build-changed-lines.ts 6.3 KB runs code
- scripts/findings-ledger.test.ts 14 KB runs code
- scripts/findings-ledger.ts 16 KB runs code
- scripts/list-fix-rubric-agents.sh 1.4 KB runs code
- scripts/review-scope.test.ts 4.1 KB runs code
- scripts/review-scope.ts 4.0 KB runs code
- scripts/tsconfig.json 181 B
- scripts/validate-findings.test.ts 23 KB runs code
- scripts/validate-findings.ts 18 KB runs code
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.
- today Changed d23a8b4fa437
- 3d ago First seen · 400 lines · 63 tokens per session scan A 911101d010bd
pr-review-engine is a skill published in the GitHub repository morpho-org/sdks (40 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 7,955 once invoked, about $0.0003 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-01.
Other skills, from other repositories
apollo-router
Version-aware guide for configuring and running Apollo Router for federated GraphQL supergraphs. Generates correct YAML for both Router v1.x and v2.x. Use this skill when: (1) setting up Apollo Router to run a supergraph, (2) configuring routing, headers, or CORS, (3) implementing custom plugins (Rhai scripts or…
apollo-router-plugin-creator
Guide for writing Apollo Router native Rust plugins. Use this skill when: (1) users want to create a new router plugin, (2) users want to add service hooks (routerservice, supergraphservice, executionservice, subgraphservice), (3) users want to modify an existing router plugin, (4) users need to understand router…
apollo-client
Guide for building React applications with Apollo Client 4.x. Use this skill when: (1) setting up Apollo Client in a React project, (2) writing GraphQL queries or mutations with hooks, (3) configuring caching or cache policies, (4) managing local state with reactive variables, (5) troubleshooting Apollo Client errors…
apollo-server
Guide for building GraphQL servers with Apollo Server 5.x. Use this skill when: (1) setting up a new Apollo Server project, (2) writing resolvers or defining GraphQL schemas, (3) implementing authentication or authorization, (4) creating plugins or custom data sources, (5) troubleshooting Apollo Server errors or…
apollo-connectors
Guide for integrating REST APIs into GraphQL supergraphs using Apollo Connectors with @source and @connect directives. Use this skill when the user: (1) mentions "connectors", "Apollo Connectors", or "REST Connector", (2) wants to integrate a REST API into GraphQL, (3) references @source or @connect directives, (4)…
apollo-federation
Guide for authoring Apollo Federation subgraph schemas. Use this skill when: (1) creating new subgraph schemas for a federated supergraph, (2) defining or modifying entities with @key, (3) sharing types/fields across subgraphs with @shareable, (4) working with federation directives (@external, @requires, @provides…