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/non-vacuous-verification)<a href="https://agentmods.dev/rules/prisma/orm/non-vacuous-verification"><img src="https://agentmods.dev/badge/rules/prisma/orm/non-vacuous-verification/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/non-vacuous-verification"><img src="https://agentmods.dev/badge/rules/prisma/orm/non-vacuous-verification.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.00342 |
| Opus 5.5 | $0.00000 | $0.00137 |
| Sonnet 5.5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
non-vacuous-verification 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 1mo 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
Non-vacuous verification
A verification that cannot fail converts absence of evidence into false confidence. Before trusting a green result, name what would have made it red.
- A regression test must be red before the fix — run it against the unfixed code and record the failure. If the triggering scenario cannot be reproduced (e.g. a transport race), don't ship a test that is green in both worlds: make the seam testable and test the seam directly.
- A verifier must fail (or loudly warn) on empty input. "All 0 known cases verified" is a discovery failure, not a pass.
- Guard type tests against
anypoisoning.skipLibCheck+ an unresolvable import in a fixture.d.tsmakes every dependent assertion vacuous (T & anyisany). Add anot.toBeAny()sentinel on the fixture's central types. - Comments are not evidence. A comment describing a guard does not mean it exists — read the code it claims to describe; correct the comment when it lies.
- Generated files: test claims by regenerating. Reading the generator is not evidence; running it is.
- Instrument before designing a fix for a hard-to-reproduce failure — a counter proving "this catch never runs" kills a wrong hypothesis in one run.
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.
- 1mo ago First seen · 21 lines · 0 tokens per session scan A 17c711dcf096
non-vacuous-verification is a cursor rule published in the GitHub repository prisma/orm (47,671 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 342 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-08-30.
Other cursor rules, from other repositories
prisma
Prisma database patterns and conventions for Next.js and TypeScript projects.
typescript-style
TypeScript style — prefer arrow functions and consistent callbacks.
drizzle-patterns
Drizzle ORM patterns and database conventions.
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
windsurfrules
Node.js ESM + EloquentJS ORM + PostgreSQL/MongoDB + Express/Fastify.
code-validation-workflow
Code validation workflow (format, lint, test, coverage, typecheck).