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/required-key-undefined-fields)<a href="https://agentmods.dev/rules/prisma/orm/required-key-undefined-fields"><img src="https://agentmods.dev/badge/rules/prisma/orm/required-key-undefined-fields/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/required-key-undefined-fields"><img src="https://agentmods.dev/badge/rules/prisma/orm/required-key-undefined-fields.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.00264 |
| Opus 5.5 | $0.00000 | $0.00106 |
| Sonnet 5.5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
required-key-undefined-fields 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 1mo 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
Required keys typed | undefined for internal input types
On internal construction-input types (IR node inputs, producer→builder handoff types), a value that may legitimately be absent is a required key typed | undefined, not an optional key:
// Do
readonly withCheck: string | undefined;
// Don't
readonly withCheck?: string;
Every construction site then states the absence explicitly (withCheck: undefined) instead of silently omitting the key — an omitted field is a compile error, so a new field can never be silently skipped by an existing caller.
Scope
- Applies to internal inputs:
*IRInput,*SchemaNodeInput, entity constructor inputs, producer→builder IR types. - Does NOT apply to user-facing authoring options or machine-rendered literals (e.g. generated migration source), where omission is the natural spelling — type those with optional keys.
- Do not restate this convention in doc comments on each type; the declaration (
x: T | undefined) already says it.
Related: use-if-defined.mdc (spreading optional values into such objects).
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.
- 1mo ago First seen · 28 lines · 0 tokens per session scan A bf6b7b27cb47
required-key-undefined-fields is a cursor rule published in the GitHub repository prisma/orm (47,697 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 264 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-09-03.
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.
rust
Rules for writing Rust services at PostHog. Focuses on writing async Rust with Tokio and encoding general Rust best practices from the Rust book and docs.
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
manage-hierarchical-resources
Cursor rule "manage-hierarchical-resources" from PaulJPhilp/EffectPatterns, covering manage hierarchical resources and example.
sqlalchemy
SQLAlchemy database patterns and conventions.