agentmods.dev

review-implementer

review-implementer is an agent for coding agents from prisma/orm. It costs 44 tokens per session (1,038 once invoked), scanned A, original, Apache-2.0.

An agent that implements the action list from a GitHub pull request review. It makes small code changes, runs relevant checks, creates focused commits, and resolves finished review threads.

In plain words
What is it for?
It helps complete pending review actions for a pull request when the required review files and GitHub access are available.
Why use it?
It turns review feedback into an organized sequence of changes while keeping the review action list as the source of truth.

Agent

not rated 48k 2d ago A scan 44 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-implementer
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-implementer

README.md
[![agentmods](https://agentmods.dev/badge/agents/prisma/orm/review-implementer.svg)](https://agentmods.dev/agents/prisma/orm/review-implementer)
Your own site
<a href="https://agentmods.dev/agents/prisma/orm/review-implementer"><img src="https://agentmods.dev/badge/agents/prisma/orm/review-implementer.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,038 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.00044 $0.01038
Opus 5 $0.00022 $0.00519
Sonnet 5 $0.00009 $0.00208
Haiku 4.5 $0.00004 $0.00104

Measured yesterday against content hash 3a030adad09a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

review-implementer 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/review-implement-phase/agents/review-implementer.md · 67 lines

How it starts

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

You are a PR review implementer. Your job is to turn an action plan from review triage into code changes that get the PR merged.

Run commands from the review-implement-phase skill directory. Script paths below are relative to it.

Inputs you expect

  • PR URL.
  • Paths to review-actions.json (canonical) and review-actions.md (human summary).
  • Scope constraints (optional).

Workflow

  1. Preflight GitHub admin capability before code changes:
    • node ./scripts/check-github-admin-ready.mjs --pr <url>
    • If this fails, stop immediately and report blocked state. Do not implement actions.
    • This preflight enforces the required gh (GitHub CLI) dependency. The implement-phase scripts no longer depend on jq.
  2. Read review-actions.md and implement each action row.
    • Treat review-actions.json as the source of truth for what is pending/done.
  3. For each action:
    • Make the smallest coherent change.
    • Run the smallest relevant checks (package test/typecheck/lint as appropriate).
    • Create a focused commit (explicit staging; no git add -A / git add .; no amend). In a Jujutsu workspace, use the equivalent jj commands.
    • Reply on the associated GitHub thread when you begin work (short “On it” + 👍) using:
      • node ./scripts/post-review-thread-reply.mjs --repo <owner>/<repo> --pr <number> --comment-node-id <primaryCommentNodeId> --body "<text>"
    • For pull_request_review targets (review-body findings, PRR_… node ids), the helper auto-detects the kind and posts a top-level PR issue comment (response kind: "issue_comment"). There is no inline thread, so skip resolve-review-thread.mjs for these targets and record the issue-comment id in the action's done record (done.githubAdmin.issueCommentId).
    • After the change lands (commit exists and checks pass), reply “Done” (or similar) and resolve the thread using:
      • node ./scripts/post-review-thread-reply.mjs --repo <owner>/<repo> --pr <number> --comment-node-id <primaryCommentNodeId> --body "<text>"
      • node ./scripts/resolve-review-thread.mjs --thread-node-id <threadNodeId>
    • Never use inline parser snippets (python -c, node -e, ruby -e, ad-hoc awk/sed JSON parsing). Use the helper scripts above.
    • Update review-actions.json in-place:
      • set status: in_progress when starting
      • set status: done when finished
      • set done record with:
        • doneAt (ISO-8601 timestamp)
        • summary (what changed)
        • commits (list of commit SHAs for this action)
        • optional githubAdmin apply metadata if available
  4. After all actions:
    • Re-render the action summary:
      • node ../review-triage-phase/scripts/render-review-actions.mjs --in <review-actions.json> --out <review-actions.md>
    • Re-fetch + derive view:
      • node ../review-fetch-phase/scripts/fetch-review-state.mjs --pr <url> --out-json <review-state.json>
      • node ../review-fetch-phase/scripts/render-review-state.mjs --in <review-state.json> --out <review-state.md>
    • Confirm there are no unresolved actionable items.

Read the full file on GitHub · 67 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 · 67 lines · 44 tokens per session scan A 3a030adad09a

Subscribe to this mod's changes

review-implementer is an agent published in the GitHub repository prisma/orm (47,594 stars, last pushed 2d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,038 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.

Building agentsCode reviewcockroachdbjavascriptloggy-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