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/config-validation-and-normalization)<a href="https://agentmods.dev/rules/prisma/orm/config-validation-and-normalization"><img src="https://agentmods.dev/badge/rules/prisma/orm/config-validation-and-normalization/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/config-validation-and-normalization"><img src="https://agentmods.dev/badge/rules/prisma/orm/config-validation-and-normalization.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.00979 |
| Opus 5.5 | $0.00000 | $0.00392 |
| Sonnet 5.5 | $0.00000 | $0.00196 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
config-validation-and-normalization 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 21d 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config Validation and Normalization
Responsibilities are split across exactly three places. Keep them there.
defineConfig() — normalize and stamp, never throw
defineConfig (in @internal/config/config-types) is the ONLY place normalization happens. It applies defaults (e.g. contract.output), stamps the non-enumerable config-format version marker, and returns the normalized config. It does NOT validate structure and never throws — a throw here happens at module-evaluation time, which would turn every structural problem into an all-commands-fail evaluation error and defeat per-section diagnostics.
The marker does not survive spreads: configs must export the defineConfig result directly. The loader rejects unmarked configs with CONFIG.VERSION_MARKER_MISSING.
The orm section schema — validate and resolve paths
The shape of the orm section is declared once, as ormConfigSchema in @internal/config-loader/src/orm-section.ts, with the CLI engine's configSchema (arktype plus a path keyword). Every structural rule lives there: descriptor fields, cross-descriptor familyId/targetId agreement, contract source shape, formatter values, and which fields are paths. Do not add a hand-written check next to it.
The engine derives everything from the declaration: validation, a CLI.CONFIG_FIELD_INVALID diagnostic per bad field naming the field and the file to fix, and the resolution of every path field against the config file that declared it (prisma-cli ADR 0005). The validated value has absolute paths, migrations.dir and contract.output defaulted, and baseDir, the directory of the nearest config file. A relative path default is declared as a thunk, ['path', '=', () => './migrations'], never as a literal.
Loader — evaluate, then report per-section diagnostics
loadConfigFiles (in @internal/config-loader) evaluates prisma.config.ts with c12 and returns each file on the chain with its sections as written. The ORM's bin hands those files to the engine, which validates the orm section with their provenance before a command runs.
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.
- 21d ago Changed · -1 lines 4354f4909f36
- 1mo ago First seen · 58 lines · 0 tokens per session scan A 095beca905d7
config-validation-and-normalization is a cursor rule published in the GitHub repository prisma/orm (47,693 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 979 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-08-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.
nextjs-standards
Cursor rule "nextjs-standards" from solana-foundation/solana-com, covering authoritative guidelines, code style, file & folder conventions, rendering strategy and state & data.
config-reload-jackspeak-issues
Config reload and JackSpeak caching issues.
linting-error-handler
Fixing common linting errors (unused vars, imports, type guards).
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.