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 agentmods add rules/prisma/orm/shared-plane-packagesgit 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/shared-plane-packages)<a href="https://agentmods.dev/rules/prisma/orm/shared-plane-packages"><img src="https://agentmods.dev/badge/rules/prisma/orm/shared-plane-packages.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.00000 | $0.01153 |
| Opus 5 | $0.00000 | $0.00576 |
| Sonnet 5 | $0.00000 | $0.00231 |
| Haiku 4.5 | $0.00000 | $0.00115 |
Grade A, and why
shared-plane-packages 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 2d 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:
- shared-plane-packages — 91% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shared Plane Packages
Overview
Shared plane packages contain side-effect-free code (types, validators, factories) that can be safely imported by both migration-plane (authoring, emitter, targets) and runtime-plane (lanes, runtime, adapters) packages. This pattern allows runtime-plane packages to import type definitions without violating plane boundaries.
When to Create a Shared Plane Package
Create a shared plane package when:
- Types are needed by both planes: Type definitions that are used by both migration-plane (e.g., emitter, authoring) and runtime-plane (e.g., lanes, runtime) packages
- Validators are pure: Arktype validators that perform structural validation without side effects
- Factories are pure: Factory functions that construct data structures without IO or external dependencies
- No migration-specific logic: The package contains no code that depends on migration-plane concerns (file I/O, pack loading, emitter hooks)
Examples
SQL Contract Types (@internal/sql-contract)
Located at packages/sql/contract/ (shared plane):
- Types:
SqlContract,SqlStorage,StorageTable,ModelDefinition - Validators: Arktype validators for contract structures
- Factories: Pure factory functions for constructing contract IR
Used by:
- Migration plane: authoring, emitter (for validation and IR construction)
- Runtime plane: lanes, runtime (for type definitions)
SQL Operations Types (planned: @internal/sql-operations)
When moved to shared plane at packages/sql/operations/:
- Types:
LoweringSpec,OperationSignature - Assembly: Pure function
assembleOperationRegistry(manifests)that takes plain manifest objects - Validators: (optional) Arktype validators for operation manifests
Used by:
- Migration plane: emitter (for assembling operations from extension packs)
- Runtime plane: lanes, runtime (for operation type definitions)
Package Structure
Shared plane packages follow this structure:
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.
- 2d ago First seen · 138 lines · 0 tokens per session scan A bf0dd9a14271
shared-plane-packages is a cursor rule published in the GitHub repository prisma/orm (47,606 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,153 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
sql-types-imports
Canonical import paths for SQL types.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
cli-error-handling
CLI command error handling patterns.
sql-queries-not-asts
Name built-and-lowered SQL units "queries", not "asts".
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).