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 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/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/skills/prisma/orm/triage-contributor-pr"><img src="https://agentmods.dev/badge/skills/prisma/orm/triage-contributor-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector pass
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.00131 | $0.03656 |
| Opus 5.5 | $0.00052 | $0.01462 |
| Sonnet 5.5 | $0.00026 | $0.00731 |
| Haiku 4.5 | $0.00013 | $0.00366 |
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 24d 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 — 218 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.
Shell constraint
A PreToolUse hook in agent shells (.claude/scripts/enforce-tools.mjs) rejects any Bash command that contains the word npm or npx followed by a space or a line end, including inside a heredoc body or a search pattern. Write a report or draft reply that mentions either word with the editor tool rather than a heredoc. To search a diff for it, use a pattern such as n[p]m.
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.
Save the open queue once:
mkdir -p wip/pr-triage
gh pr list --repo prisma/orm --state open --limit 1000 \
--json number,title,author,isCrossRepository,baseRefName,updatedAt,isDraft \
> wip/pr-triage/queue.json
--limit 1000 sits above the current queue size; it is not a guarantee. If queue.json holds exactly that many PRs the list is truncated, so raise the limit and re-run before trusting the result.
A fork PR (isCrossRepository) is always external, but a PR from a branch on prisma/orm itself can be external too: former staff keep branches they pushed while they had write access. The doc's Who counts as external has the rule. When triaging the whole queue, check the permission and profile bio of every same-repo author:
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.
- 24d ago Changed · +28 lines 4aaf417e3fc9
- 1mo ago Changed fe4c23ef6b7c
- 1mo 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,697 stars, last pushed today), licensed Apache-2.0. It adds 131 tokens to every session and 3,656 once invoked, about $0.0005 per session on Opus 5.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
reviewing-personhog-protocol
The full review process for personhog coordination-protocol changes — leases, fencing, handoffs, supervisors, failure budgets, warming, and changelog semantics. Use before pushing or requesting review on any personhog protocol changeset, when asked for an exhaustive or careful review of personhog code, and after any…
prisma-orm
Use when modeling data or writing type-safe queries with Prisma ORM in TypeScript — schema.prisma, prisma.config.ts, the generated Prisma Client, and Prisma Migrate, including the v6 to v7 upgrade. NOT schema-as-TS with a SQL builder (that is drizzle-orm), NOT ORM-agnostic zero-downtime migration (that is…
dev-self-merge
Merge self-check for a green PR. Reads the PR's required-check status from the checks API (the committed ci-status feed is RETIRED), outputs MERGE (mark task completed, stand down — server-side auto-enqueue enqueues.
pr-conflict-refresh
Find every open PR that is CONFLICTING/DIRTY against current main after a merge wave, ping its assigned dev to merge main into their branch and push, and track the re-test status.
qa-team
Multi-agent QA review team for code changes. This skill should be used when the user asks to "review my code", "run QA", "qa-team", "review this branch", "code review", "check my changes", or wants a comprehensive multi-perspective code review of the current branch's changes. Spawns parallel specialist agents…
git-step-commit
Analyze Git changes, split them into coherent commits, infer message language and format, optionally close supplied GitHub issues, and execute safely. Manage persistent global or repository preferences for review versus direct submission and automatic or specified commit-message language through native Git config.…