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/use-timeouts-helper-in-tests)<a href="https://agentmods.dev/rules/prisma/orm/use-timeouts-helper-in-tests"><img src="https://agentmods.dev/badge/rules/prisma/orm/use-timeouts-helper-in-tests.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.00300 |
| Opus 5 | $0.00000 | $0.00150 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
use-timeouts-helper-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 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
Use Timeouts Helper In Tests
When a test needs an explicit timeout, always use a shared named helper from @repo/test-utils (for example timeouts.spinUpPpgDev).
Do
- Use
timeouts.*constants instead of raw numbers. - Keep timeout values centralized in
@repo/test-utils.
Don't
- Don't write raw numeric timeout values in test bodies (for example
{ timeout: 1_000 }).
Exception: facade-only examples
An example that models a real application depends on one @prisma/orm-* facade and nothing else (ADR 242), so it cannot have @repo/test-utils — a workspace package with no published counterpart. Naming both roots in one consumer also loads two copies of every module they share, which scripts/lint-single-import-root.mjs rejects.
Those examples keep the same shape locally: a test/timeouts.ts exporting one named constant per scenario, applying TEST_TIMEOUT_MULTIPLIER the way the shared helper does. Pattern reference: examples/mongo-blog-leaderboard/test/timeouts.ts.
The rule is unchanged for every other test: a named constant, never a raw number at the call site.
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 · 27 lines · 0 tokens per session scan A 76ac80fa3909
use-timeouts-helper-in-tests 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 300 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
use-timeouts-helper-in-tests
Use shared timeout helpers in tests.
mongodb-memory-server-setup
When adding mongodb-memory-server (MMS) to a package or writing tests that use it, follow these rules to prevent CI failures.
use-hash-constructors
Use coreHash() and profileHash() constructors instead of 'as never' casts for branded hash types.
test-file-organization
Test file organization and splitting guidelines.
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.
typed-contract-in-tests
Use typed Contract from fixtures in integration tests.