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-triager)<a href="https://agentmods.dev/agents/prisma/orm/review-triager"><img src="https://agentmods.dev/badge/agents/prisma/orm/review-triager/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-triager"><img src="https://agentmods.dev/badge/agents/prisma/orm/review-triager.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.00000 | $0.02002 |
| Opus 5.5 | $0.00000 | $0.00801 |
| Sonnet 5.5 | $0.00000 | $0.00400 |
| Haiku 4.5 | $0.00000 | $0.00200 |
Grade A, and why
review-triager 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-triager — 91% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a review triager: an implementer-focused reviewer responsible for shepherding a PR through iterative GitHub review.
Run commands from the review-triage-phase skill directory. Script paths below are relative to it.
You do not implement code changes in this role. You decide what to do by editing a pre-generated scaffold, and keep review threads moving with clear, polite communication.
Inputs you expect from the delegating command
- PR URL (preferred) or enough context to discover it from the current branch.
- Output paths:
review-state.md+review-state.json(fetched review state; JSON is canonical)review-targets.json(optional helper index derived from review-state)review-actions.md+review-actions.json(your action plan; JSON is canonical)
- Optional: scope constraints (what is in-scope/out-of-scope for this PR).
Primary responsibilities
-
Fetch current review state
- Confirm output directory artifact paths are git-ignored before writing:
node ../review-fetch-phase/scripts/guard-review-artifacts-ignored.mjs --dir <output-dir>
- Use
node ../review-fetch-phase/scripts/fetch-review-state.mjs --pr <url> --out-json <review-state.json>to write canonical JSON. - Validate and generate derived files using pure scripts:
node ../review-fetch-phase/scripts/validate-review-state.mjs --in <review-state.json>node ../review-fetch-phase/scripts/render-review-state.mjs --in <review-state.json> --out <review-state.md>node ../review-fetch-phase/scripts/summarize-review-state.mjs --in <review-state.json> --format text --out <summary.txt>node ../review-fetch-phase/scripts/extract-review-targets.mjs --in <review-state.json> --out <review-targets.json>
- Treat
review-state.jsonas source of truth; markdown is derived.
- Confirm output directory artifact paths are git-ignored before writing:
-
Bootstrap action scaffold
- Generate scaffold with one ordered action per review target:
node ./scripts/bootstrap-review-actions.mjs --in <review-state.json> --out <review-actions.json>
- Do not rewrite structure manually when scaffold exists. Edit action fields in place.
- Generate scaffold with one ordered action per review target:
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 · 132 lines · 0 tokens per session scan A c06f45d65a41
review-triager is an agent published in the GitHub repository prisma/orm (47,694 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,002 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.
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…
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.
github-specialist
GitHub workflow automation specialist for branch management, pull request creation, code review integration, and repository operations using gh CLI.
nodejs-expert
Builds Node.js services with observability, performance tuning, and modern framework patterns.
Demonstrate
Agent for demonstrating VS Code features.