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/typed-contract-in-tests)<a href="https://agentmods.dev/rules/prisma/orm/typed-contract-in-tests"><img src="https://agentmods.dev/badge/rules/prisma/orm/typed-contract-in-tests/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/typed-contract-in-tests"><img src="https://agentmods.dev/badge/rules/prisma/orm/typed-contract-in-tests.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.01094 |
| Opus 5.5 | $0.00000 | $0.00438 |
| Sonnet 5.5 | $0.00000 | $0.00219 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
typed-contract-in-tests 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 8d 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:
- typed-contract-in-tests — 97% identical, 26 lines differ
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use Typed Contract in Integration Tests
Rule
Integration tests should import the typed Contract from fixtures/contract.d.ts instead of using the generic SqlContract<SqlStorage> type. This provides proper type inference for tables, columns, and query results.
The Problem
Using generic contract types loses type information:
// ❌ WRONG: Generic type loses inference
import type { SqlContract, SqlStorage } from '@internal/sql-contract/types';
function loadContractFixture(): SqlContract<SqlStorage> {
// ...
}
// Later in tests:
const tables = schema(context).tables;
const userTable = tables['user']!; // Needs non-null assertion
const userColumns = userTable.columns;
const plan = sql({ context })
.from(userTable)
.select({ id: userColumns['id']!, email: userColumns['email']! }) // Needs bracket access + assertions
.build({ params: { cursor: 5 } });
const rows = await executePlanAndCollect(runtime, plan);
expect(rows.map((r) => r['id'] as number)).toEqual([6, 7, 8, 9, 10]); // Needs type cast
The Solution
Import the typed Contract from the fixtures directory and name it where the JSON enters. A test that builds a client passes the JSON through the target's contractFromJson and gives the result to the client, which infers the contract type from it:
// ✅ CORRECT: the client infers Contract from the typed value
import postgres from '@internal/postgres/runtime';
import { contractFromJson } from '@internal/postgres/static';
import type { Contract } from './fixtures/contract.d';
import contractJson from './fixtures/contract.json' with { type: 'json' };
const db = postgres({ contract: contractFromJson<Contract>(contractJson), url });
Never write the type argument on the client (postgres<Contract>(...)): the clients take only { contract }.
A test that needs a contract without a client validates the JSON with validateSqlContractFully:
// ✅ CORRECT: Typed contract provides full inference
import type { Contract } from './fixtures/contract.d';
function loadContractFixture(): Contract {
const fixtureDir = dirname(fileURLToPath(import.meta.url));
const contractPath = join(fixtureDir, 'fixtures/contract.json');
const json = readFileSync(contractPath, 'utf8');
const contractJson = JSON.parse(json) as unknown;
return validateSqlContractFully<Contract>(contractJson);
}
// Later in tests:
const { user } = schema(context).tables; // Destructure directly
const plan = sql({ context })
.from(user)
.select({ id: user.columns.id, email: user.columns.email }) // Direct property access
.where(user.columns.id.gt(param('cursor')))
.build({ params: { cursor: 5 } });
const rows = await executePlanAndCollect(runtime, plan);
expect(rows.map((r) => r.id)).toEqual([6, 7, 8, 9, 10]); // r.id is typed as number
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.
- 8d ago Changed · +14 lines 840e6f865a49
- 21d ago Changed bd7572757539
- 1mo ago First seen · 116 lines · 0 tokens per session scan A 76cc20070533
typed-contract-in-tests is a cursor rule published in the GitHub repository prisma/orm (47,671 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,094 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
react-query-tests
// ✅ CORRECT: Legacy React Query pattern const ctx = konn() .beforeEach(() => createAppRouter()) .afterEach((ctx) => ctx?.close?.()) .done().
tanstack-react-query-tests
// ✅ CORRECT: Use await using for automatic cleanup await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
testing
Test conventions for openapi-to-cli (Jest).
prisma
Prisma database patterns and conventions for Next.js and TypeScript projects.
benchmark
Measure and repair Plate/Plite performance, or review a performance design before running its applicable benchmark lanes. Use before writing, reviewing, running, rerunning, checking, skipping or deferring a performance gate, including a plan's scale gate, before writing a benchmark script, before explaining a…