agentmods.dev

review-orchestrator

review-orchestrator is an agent for Claude Code from prisma/orm. It costs 0 tokens per session (626 once invoked), scanned A, original, Apache-2.0.

An automated coordinator for repeatedly checking a GitHub pull request, sorting review comments, applying fixes, and resolving completed discussion threads.

In plain words
What is it for?
Use it to fetch review status, triage comments, implement requested changes, and continue until no actionable feedback remains.
Why use it?
It removes the manual work of tracking review feedback across several rounds.

Agent for Claude Code ✓ vendor

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

not rated 48krepo +7 today A scan 0 tokens original Apache-2.0

Good fit Use it to fetch review status, triage comments, implement requested changes, and continue until no actionable feedback remains.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/prisma/orm/review-orchestrator
View source ↗ prisma/orm prisma.io
About the project

Prisma ORM is a Node.js and TypeScript database toolkit that lets applications work with databases through a programming interface instead of writing every query directly in SQL. Developers use it with databases including PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB, and CockroachDB. The catalogue add-ons provide agent rules, skills, hooks, agents, and other workflows for using Prisma.

prisma/orm · 47,697 stars · on GitHub · prisma.io

Install

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.

Clone the repo
git clone --depth 1 https://github.com/prisma/orm

Made for: Claude Code.

Wrote 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.

agentmods badge for review-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/prisma/orm/review-orchestrator/github.svg)](https://agentmods.dev/agents/prisma/orm/review-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/prisma/orm/review-orchestrator"><img src="https://agentmods.dev/badge/agents/prisma/orm/review-orchestrator/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.

agentmods 80×15 button for review-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/prisma/orm/review-orchestrator"><img src="https://agentmods.dev/badge/agents/prisma/orm/review-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 626 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00626
Opus 5.5 $0.00000 $0.00250
Sonnet 5.5 $0.00000 $0.00125
Haiku 4.5 $0.00000 $0.00063

Measured 1mo ago against content hash 51617a13f86f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review-orchestrator 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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills-contrib/github-review-iteration/agents/review-orchestrator.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the review orchestrator. You coordinate the triager and implementer to drive a PR to merge.

Run commands from this skill's directory. All script paths below are relative to it. Sibling skills are located in the same parent directory (use ../ to reach them).

Primary loop (repeat until clear)

  1. Fetch review state (JSON-first)

    • node ../review-fetch-phase/scripts/fetch-review-state.mjs --pr <url> --out-json <output-dir>/review-state.json
    • node ../review-fetch-phase/scripts/render-review-state.mjs --in <output-dir>/review-state.json --out <output-dir>/review-state.md
    • node ../review-fetch-phase/scripts/summarize-review-state.mjs --in <output-dir>/review-state.json --format text --out <output-dir>/summary.txt
    • Treat review-state.json as canonical for triage.

  2. Triage

    • Delegate to review-triager.
    • Output: review-actions.json (canonical) and review-actions.md (human summary).
    • Ensure GH thread administration is performed:
      • 👍 + “will address” for items that will be implemented (leave unresolved)
      • 👎 + explanation + resolve for items not addressed in this PR

  3. Inspect action state

    • Read review-actions.json after triage.
    • If no will_address actions remain with pending or in_progress status, stop and report completion.
    • Only delegate implementation when at least one pending will_address action exists.

  4. Implement

    • Delegate to review-implementer to execute review-actions.md.
    • Enforce granular commits and explicit staging.
    • Ensure the implementer updates review-actions.json statuses and done completion records.
    • Ensure each action maps to a GH thread:
      • “On it” + 👍 when starting
      • “Done” + resolve when finished

  5. Re-fetch and verify

    • Re-run fetch-review-state.
    • If unresolved actionable threads remain, loop.
    • If none remain, stop and report completion.

Guardrails

  • Keep review artifacts and scripts out of unrelated PR branches.
  • Never stage/commit broad untracked directories as a side effect of review automation.
  • Prefer resolving threads only when the PR either (a) implemented the fix, or (b) explicitly won’t address in this PR with explanation.
  • Use deterministic storage layout: wip/reviews/<owner>_<repo>_pr-<number>/.
  • Use node-id-only action targets (target.nodeId), never numeric database ids.

Read the full file on GitHub · 53 lines

Changes

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.

  1. 1mo ago First seen · 53 lines · 0 tokens per session scan A 51617a13f86f

Subscribe to this mod's changes

review-orchestrator is an agent published in the GitHub repository prisma/orm (47,697 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 626 tokens. 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.

Code reviewDatabasesGit and workflowTypeScriptjavascriptnodejsormprisma
Related

Other agents, from other repositories

workflow-quality

Use this agent when you need expert guidance on Output SDK implementation patterns, code quality, and best practices. Invoke when writing or reviewing workflow code, troubleshooting implementation issues, or ensuring code follows SDK conventions.

growthxai/output · 43 tokens

code-reviewer

Use this agent when you need expert code review of recently written or modified code. This agent should be invoked after completing a logical chunk of functionality, implementing a new feature, fixing a bug, or making significant changes to existing code. The agent focuses on collaborative improvement rather than…

PostHog/posthog · 415 tokens

pr-review-governance-checker

Reviews one pinned change for the governance discipline, checking mechanical conformance to rules the repository documents, such as naming, structure, and required files and sections, and returns anchored findings.

wahidyankf/ose-public · 44 tokens

github-specialist

GitHub workflow automation specialist for branch management, pull request creation, code review integration, and repository operations using gh CLI.

FortiumPartners/ensemble · 28 tokens

nodejs-expert

Builds Node.js services with observability, performance tuning, and modern framework patterns.

NickCrew/Claude-Cortex · 22 tokens

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens