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.
npx agentmods add skills/prisma/orm/triage-contributor-prnpx skills add prisma/orm --skill triage-contributor-prgit 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/skills/prisma/orm/triage-contributor-pr)<a href="https://agentmods.dev/skills/prisma/orm/triage-contributor-pr"><img src="https://agentmods.dev/badge/skills/prisma/orm/triage-contributor-pr.svg" alt="Measured on agentmods" 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 | $0.00131 | $0.02934 |
| Opus 5 | $0.00066 | $0.01467 |
| Sonnet 5 | $0.00026 | $0.00587 |
| Haiku 4.5 | $0.00013 | $0.00293 |
Grade A, and why
triage-contributor-pr scanned grade A with 1 finding 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 2d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
grep -nE "^\+.*(postinstall|preinstall|prepare\"|child_process|execSync|spawn\(|eval\(|atob\(|fetch\(|https?://|pull_request_target|secrets\.|permissions:)" wip/pr-triage/diff-*.patch How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage external contributor PRs
Decide what happens to unsolicited pull requests from outside the maintainer team, and report each verdict with the evidence behind it.
The criteria are in docs/oss/pr-triage.md. Read that file first — this skill is the procedure for applying it, not a second copy of it. When the two disagree, the doc wins.
When to use
- "Triage the open contributor PRs"
- "Evaluate the PRs from "
- "Is it safe to approve CI on #NNNNN?"
- "Which contributor PRs are stale?"
Scope
Report, do not act. Produce verdicts, evidence, and draft replies. Do not close a PR, post a comment, approve a workflow run, or push to a contributor's branch unless the maintainer asks for that as a separate step. Approving CI in particular is the maintainer's call — your job is to give them what they need to make it.
Procedure
1. Build the list
GitHub logins are case-sensitive in a jq comparison and users do capitalize unpredictably (Develop-KIM, not Develop-Kim). Lowercase both sides or you will silently drop PRs.
Set AUTHORS from whoever the maintainer named, lowercased. Leave it as [] to triage the whole external queue — never leave a list from a previous run in place, and never treat the example list as the scope. Pipe to a real jq: gh's built-in --jq has no --argjson.
AUTHORS='["snowingfox","wehamed"]' # or '[]' for every external contributor
gh pr list --repo prisma/prisma --state open --limit 1000 \
--json number,title,author,isCrossRepository,baseRefName,updatedAt,isDraft \
| jq -r --argjson authors "$AUTHORS" '.[]
| select($authors == [] or ([.author.login | ascii_downcase] | inside($authors)))
| select($authors != [] or .isCrossRepository)
| "\(.number)\t\(.author.login)\t\(.baseRefName)\t\(.updatedAt)\t\(.title)"'
isCrossRepository is what makes a PR external — it came from a fork. gh pr list does not expose authorAssociation, so do not reach for it.
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.
- 2d ago First seen · 190 lines · 131 tokens per session scan A 19fdf49ecb9f
triage-contributor-pr is a skill published in the GitHub repository prisma/orm (47,601 stars, last pushed 2d ago), licensed Apache-2.0. It adds 131 tokens to every session and 2,934 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
prisma-next-migrations
Author Prisma Next migrations — choose db update vs migration plan, edit the framework-rendered migration.ts (replace placeholder sentinels with dataTransform closures), recover from MIGRATION.HASHMISMATCH or PN-MIG-2001 unfilled placeholder. Use for prisma migrate dev, prisma migrate deploy, prisma db push, db…
prisma-next-contract
Edit the Prisma Next data contract — add models, fields, relations, indexes, enums, value objects (composite types), type aliases, namespaces (Postgres schemas), cross-contract foreign keys (cross-space FK), polymorphic types (@@discriminator / @@base), use extension namespaces (pgvector.Vector(...)…
prisma-next-quickstart
Adopt Prisma Next into a new project, onto an existing database, or as the first move after a bootstrap tool dropped you into a scaffold. Use for "what can I do with Prisma Next", "what can I do next with Prisma", "where do I start", "what should I do first", "just ran createprisma", "createprisma", "npx…
prisma-next-migration-review
Review what Prisma Next migrations will run on merge or deploy, render the migration graph, resolve concurrent / diamond-convergence conflicts, and configure environment refs for CI. Use for "what migrations are going to run", "what runs on deploy", merge conflict, diamond convergence, concurrent migrations, migration…
prisma-next-runtime
Wire the Prisma Next runtime — db.ts setup using postgres (...) from @prisma-next/postgres/runtime, sqlite (...) from @prisma-next/sqlite/runtime, or mongo (...) from @prisma-next/mongo/runtime; middleware composition (telemetry from @prisma-next/middleware-telemetry; lints and budgets), DATABASEURL config…
prisma-next-supabase
Use Prisma Next with a Supabase project via @prisma-next/extension-supabase — wire extensions: [supabasePack], declare cross-space FKs to supabase:auth.AuthUser, author RLS policies (policyselect / policyupdate / @@rls, auth.uid() predicates), build db.ts with the supabase() factory, bind roles per request…