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/rules/prisma/orm/review-scope-overrides)<a href="https://agentmods.dev/rules/prisma/orm/review-scope-overrides"><img src="https://agentmods.dev/badge/rules/prisma/orm/review-scope-overrides.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.1 | $0.00008 | $0.00158 |
| Opus 5 | $0.00004 | $0.00079 |
| Sonnet 5 | $0.00002 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
review-scope-overrides 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 3d 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-scope-overrides — 92% identical, 2 lines differ
What it actually says
Review scope overrides
When producing local PR/branch review artifacts (walkthroughs, code reviews, design reviews), honor an explicitly-provided base/parent branch.
Rules
- If the user specifies a parent branch (e.g.
spec/psl-contract-authoring), use that as the base for the review range:origin/<base>...HEAD
- Do not “helpfully” substitute
origin/HEAD/origin/mainwhen a base is explicitly given. - If the base branch name is ambiguous (local vs remote), resolve it to
origin/<base>when possible and record the resolved range in the review artifacts.
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.
- 3d ago First seen · 17 lines · 8 tokens per session scan A 76880170893e
review-scope-overrides is a cursor rule published in the GitHub repository prisma/orm (47,608 stars, last pushed 4d ago), licensed Apache-2.0. It adds 8 tokens to every session and 158 once invoked, about $0.0000 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.
Other cursor rules, from other repositories
git-staging
Git commit best practices - avoid git add -A, stage files explicitly, always sign off.
optimize-for-human-time-on-prs
Don't open one-line / chore PRs on their own; batch ancillary work into in-flight PRs.
code-review
Prior to submitting or pushing code to Github, these steps should be reviewed.
contributing
Cursor rule "contributing" from groupultra/telegram-search, covering contribution & refactor guidelines, 1. before large changes (refactors, new infra, new domains), 2. backend mindset, 3. typescript style and 4. pr hygiene.
release-ts-sdk
Release @aptos-labs/ts-sdk or @aptos-labs/confidential-asset — version bump, changelog stamp, release PR, then tag + GitHub Release that triggers NPM publish.
workflow
Git branching strategy, commit conventions, and pull request workflow.