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.
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.
git clone --depth 1 https://github.com/prisma/ormWrote 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/agents/prisma/orm/review-implementer)<a href="https://agentmods.dev/agents/prisma/orm/review-implementer"><img src="https://agentmods.dev/badge/agents/prisma/orm/review-implementer/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/agents/prisma/orm/review-implementer"><img src="https://agentmods.dev/badge/agents/prisma/orm/review-implementer.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.00044 | $0.01038 |
| Opus 5.5 | $0.00018 | $0.00415 |
| Sonnet 5.5 | $0.00009 | $0.00208 |
| Haiku 4.5 | $0.00004 | $0.00104 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- review-implementer — 94% identical, 3 lines differ
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) andreview-actions.md(human summary). - Scope constraints (optional).
Workflow
- 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 onjq.
- Read
review-actions.mdand implement each action row.- Treat
review-actions.jsonas the source of truth for what is pending/done.
- Treat
- 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 equivalentjjcommands. - 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_reviewtargets (review-body findings,PRR_…node ids), the helper auto-detects the kind and posts a top-level PR issue comment (responsekind: "issue_comment"). There is no inline thread, so skipresolve-review-thread.mjsfor these targets and record the issue-comment id in the action'sdonerecord (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.jsonin-place:- set
status: in_progresswhen starting - set
status: donewhen finished - set
donerecord with:doneAt(ISO-8601 timestamp)summary(what changed)commits(list of commit SHAs for this action)- optional
githubAdminapply metadata if available
- set
- 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.
- Re-render the action summary:
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.
- 1mo ago First seen · 67 lines · 44 tokens per session scan A 3a030adad09a
review-implementer is an agent published in the GitHub repository prisma/orm (47,697 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 1,038 once invoked, about $0.0002 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-09-03.
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.
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…
nodejs-expert
Builds Node.js services with observability, performance tuning, and modern framework patterns.
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
js-ts-tech-lead
Use this agent when you need expert-level code review and architectural guidance for JavaScript/TypeScript projects. Examples: After implementing a new feature or module, when refactoring existing code, when designing library APIs, when establishing coding standards, or when you need to ensure code quality meets…
Demonstrate
Agent for demonstrating VS Code features.