agentmods.dev

review-orchestrator

review-orchestrator is an agent for coding agents from prisma/orm. It costs 37 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

not rated 48k 2d ago A scan 37 tokens original Apache-2.0
View the source file prisma/orm
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,594 stars · on GitHub

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.

agentmods
npx agentmods add agents/prisma/orm/review-orchestrator
Clone the repo
git clone --depth 1 https://github.com/prisma/orm

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.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.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 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. Scan, not verified.
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 $0.00037 $0.00626
Opus 5 $0.00018 $0.00313
Sonnet 5 $0.00007 $0.00125
Haiku 4.5 $0.00004 $0.00063

Measured yesterday against content hash 51617a13f86f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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. yesterday 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,594 stars, last pushed 2d ago), licensed Apache-2.0. It adds 37 tokens to every session and 626 once invoked, about $0.0002 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.

Code reviewGit and workflowcockroachdbjavascriptloggy-coreloggy-terminalmariadb
Related

Other agents, from other repositories

review-triager

Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.

prisma/prisma-next · 59 tokens

review-implementer

Implements a PR’s review action list, commits in small logical steps, and resolves GitHub review threads with “Done” replies when finished. Use when review-actions.md exists for a PR.

prisma/prisma-next · 44 tokens

review-orchestrator

Orchestrates the iterative PR review loop: fetch → triage → implement → resolve threads → re-fetch until clear. Use when a PR has active review.

prisma/prisma-next · 0 tokens

analyze-pass-impact

Analyzes how a specific topic affects a group of compiler passes. Used by the /plan-update skill to parallelize research across all compiler phases. Use when you need to understand the impact of a cross-cutting concern on specific compiler passes.

react/react · 53 tokens

json-output-reviewer

Reviews JSON output schema design, backwards compatibility, actions arrays, and machine-readability.

fallow-rs/fallow · 21 tokens

mobile-tester

Agent "mobile-tester" from akaszubski/autonomous-dev, covering mission, hard gate: appium mcp availability check, hard gate: environment security (sandbox only), hard gate: screenshot data safety and hard gate: 60-second timeout per test case.

akaszubski/autonomous-dev · 31 tokens