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/sql-types-importsgit 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/sql-types-imports)<a href="https://agentmods.dev/rules/prisma/orm/sql-types-imports"><img src="https://agentmods.dev/badge/rules/prisma/orm/sql-types-imports.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 | $0.00000 | $0.00679 |
| Opus 5 | $0.00000 | $0.00340 |
| Sonnet 5 | $0.00000 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
sql-types-imports 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 yesterday.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQL Types Import Path
CRITICAL: SQL-specific contract types (SqlContract, SqlStorage, SqlMappings, etc.) should be imported from @internal/sql-contract/types (shared plane package).
Current Import Strategy
All packages should import SQL contract types from the shared plane:
// ✅ CORRECT: Import SQL types from sql-contract (shared plane)
import type { SqlContract, SqlStorage, SqlMappings } from '@internal/sql-contract/types';
Package Structure
@internal/contract: Core contract types (ContractBase,Source) and document family types (DocumentContract)@internal/sql-contract: SQL-specific contract types (SqlContract,SqlStorage,SqlMappings,ModelDefinition,StorageTable,StorageColumn, etc.) - canonical source (shared plane)@internal/sql-operations: SQL-specific operations (OperationSignature,LoweringSpec,assembleOperationRegistry) - canonical source (shared plane, see brief 18)@internal/sql-contract-emitter: SQL emitter hook (sqlTargetFamilyHook) - canonical source@internal/operations: Target-neutral operations (OperationRegistry,ArgSpec,ReturnSpec,createOperationRegistry) - canonical source
When to Use Each Package
@internal/contract/types: Core contract types (ContractBase,Source) or document family types (DocumentContract)@internal/sql-contract/types: SQL-specific contract types (canonical source, shared plane)@internal/sql-contract/validators: SQL contract validators (shared plane)@internal/sql-contract/factories: SQL contract IR factories (shared plane)@internal/sql-operations: SQL-specific operations (canonical source, shared plane, use directly)@internal/sql-contract-emitter: SQL emitter hook (canonical source, use directly)@internal/operations: Target-neutral operations (canonical source, use directly)
Migration Notes
- All packages: Should import SQL contract types from
@internal/sql-contract/types(shared plane) - Runtime and Lanes: Can safely import from
@internal/sql-contract/typesas it's in the shared plane - Authoring and Emitter: Import from
@internal/sql-contract/typesfor types,@internal/sql-contract/validatorsfor validation - Test files: Use
@internal/sql-contract/typesand@internal/sql-contract/factoriesfor test fixtures
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.
- yesterday First seen · 52 lines · 0 tokens per session scan A 1d224db06bf2
sql-types-imports is a cursor rule published in the GitHub repository prisma/orm (47,594 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 679 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
test-database-limitations
Test databases created via withDevDatabase() from @prisma-next/test-utils use pglite (an in-memory PostgreSQL implementation via @prisma/dev). Pglite does not support PostgreSQL extensions like pgvector, pgtrgm, etc.
postgres-lateral-patterns
PostgreSQL LATERAL and jsonagg rendering patterns.
type-extraction-from-contract
Extract TypeScript types from contract.d.ts and helpers.
sql-queries-not-asts
Name built-and-lowered SQL units "queries", not "asts".
query-patterns
Standard patterns for working with Prisma Next queries.
storage-type-hooks
Use codec-owned storage-type hooks for control-plane type behavior.