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/storage-type-hooksgit 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/storage-type-hooks)<a href="https://agentmods.dev/rules/prisma/orm/storage-type-hooks"><img src="https://agentmods.dev/badge/rules/prisma/orm/storage-type-hooks.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.00185 |
| Opus 5 | $0.00000 | $0.00093 |
| Sonnet 5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
storage-type-hooks 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- storage-type-hooks — 100% identical, 0 lines differ
What it actually says
Storage Type Control Hooks
Use codec-owned control hooks for storage type behavior. Contract-defined storage types must be handled by codec owners (adapter/extension), not by adding enum-specific fields to shared IR.
Do
- Represent custom storage types via
storage.typesand columntypeRef - Implement planning/verification/introspection in codec-owned hooks
- Use schema annotations for target-specific introspection data
- Prefer adapter
format_type()output when expanding parameterized native types
Avoid
- Adding enum-specific fields to
SqlSchemaIR - Framework-level enum abstractions or codecId branching in shared SQL layers
- Treating missing type parameters as a successful match when the contract declares them
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 · 23 lines · 0 tokens per session scan A df798c397fcb
storage-type-hooks 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 185 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.
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.
contract-space-package-layout
On-disk layout for packages that expose a contract space (extensions, internal monorepo packages, aggregate-root apps).