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/never-change-the-framework-domain)<a href="https://agentmods.dev/rules/prisma/orm/never-change-the-framework-domain"><img src="https://agentmods.dev/badge/rules/prisma/orm/never-change-the-framework-domain/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/rules/prisma/orm/never-change-the-framework-domain"><img src="https://agentmods.dev/badge/rules/prisma/orm/never-change-the-framework-domain.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.00383 | $0.00383 |
| Opus 5.5 | $0.00153 | $0.00153 |
| Sonnet 5.5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
never-change-the-framework-domain 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.
What it actually says
Never change the framework domain
The framework domain is the concepts packages/1-framework defines: the contract's types (0-foundation/contract), the control and migration vocabulary (1-core/framework-components), and the interfaces families and targets implement.
Work does not add a concept to it, change what one means, or move family or target code into it so two families can share it. A design that needs this is almost certainly cutting a corner. Stop, tell the operator at once with the files and types involved, and change the design — put the work in the family or target that owns it, behind the interfaces that already exist.
The one allowed change: vocabulary that lets the framework name a concept its domain already defines. Example: a valueObjectField migration subject, because ContractValueObjectField already exists. Even then, tell the operator before building it, naming the existing type and every framework file you touch.
The test
- Does the concept already exist in the framework's types or an ADR? If not, it is new — stop.
- Would every family, and a database we do not support yet, mean the same thing by it? If it describes how one family stores data (rows, documents, stored names, columns), it does not belong.
- Is it moving into the framework only so code is shared? Then each family keeps its own; they share the framework's types, not helpers built on their storage.
Reviewers: any new or changed export in packages/1-framework is a finding until it passes this test. See also no-family-vocabulary-in-framework.mdc.
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 · 22 lines · 383 tokens per session scan A f92981ffac0d
never-change-the-framework-domain is a cursor rule published in the GitHub repository prisma/orm (47,662 stars, last pushed 2d ago), licensed Apache-2.0. It adds 383 tokens to every session, about $0.0015 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-10-30.
Other cursor rules, from other repositories
prisma
Prisma database patterns and conventions for Next.js and TypeScript projects.
typescript-style
TypeScript style — prefer arrow functions and consistent callbacks.
workflow
Workflow for openapi-to-cli.
react-components
Rules for writing React components in this project.
server-patterns
Rules for server-side Express code.
chassis
Chassis conventions — decorator-driven Express 5 + TypeScript.