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/typescript-patterns)<a href="https://agentmods.dev/rules/prisma/orm/typescript-patterns"><img src="https://agentmods.dev/badge/rules/prisma/orm/typescript-patterns.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.00465 |
| Opus 5 | $0.00000 | $0.00233 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
typescript-patterns 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 4d 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
TypeScript and Architecture Patterns
This rulecard is intentionally short. For deeper examples, see docs/reference/typescript-patterns.md.
Focused rulecards
.cursor/rules/generic-parameters.mdc— Generic parameter defaults.cursor/rules/interface-factory-pattern.mdc— Interface-based design + factory functions.cursor/rules/type-predicates.mdc— Replace blind casts with type predicates.cursor/rules/test-mocking-patterns.mdc— Type assertions and mocking patterns in tests
Quick reminders
- No blind casts in production:
as unknown as Xis forbidden outside tests. Prefer type predicates or fix the type surface. - Export interfaces; construct via factories: keep classes as private implementation details.
- No generic defaults unless meaningful: defaults are semantics, not “flexibility”.
- Test-only escapes:
@ts-expect-errorand double casts are acceptable only in test files, with a short explanation. - Key id-like string parameters on the map they come from: a
Record<string, string>constraint widens'pg/int8@1'tostring;keyof CT & stringpreserves the literal and gives completions. Reach for the keyed union whenever a string is semantically an id from a known map. ReturnTypeof an overloaded function resolves to the last overload. Adding a new last overload, or reordering the existing ones so a different signature ends up last, silently retypes everyReturnType<typeof fn>consumer; an overload inserted earlier leaves them alone. Order overloads most-specific first and most general last, and pin the inferred type with a type test so a change to the last signature fails loudly.
Related rules
.cursor/rules/no-inline-imports.mdc.cursor/rules/object-hasown.mdc.cursor/rules/prefer-assertions-over-defensive-checks.mdc
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.
- 4d ago First seen · 32 lines · 0 tokens per session scan A 44c60e2769f8
typescript-patterns is a cursor rule published in the GitHub repository prisma/orm (47,608 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 465 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
typescript-patterns
TypeScript and architecture patterns for this codebase.
tsdown-config-package-source-only
Keep @prisma-next/tsdown source-only exports.
no-bare-casts
No bare as casts in production TypeScript. Use blindCast (value) from @prisma-next/utils/casts as the auditable escape hatch, castAs (value) for declarative-only assertions, or rewrite to eliminate the cast. as const is exempt. Test files are exempt.
no-inline-imports
Prohibit inline type imports in source files.
use-hash-constructors
Use coreHash() and profileHash() constructors instead of 'as never' casts for branded hash types.
use-if-defined
Use ifDefined() for conditional object spreads.