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/tsdown-dist-layout-in-tests)<a href="https://agentmods.dev/rules/prisma/orm/tsdown-dist-layout-in-tests"><img src="https://agentmods.dev/badge/rules/prisma/orm/tsdown-dist-layout-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.00010 | $0.00187 |
| Opus 5 | $0.00005 | $0.00093 |
| Sonnet 5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
tsdown-dist-layout-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 3d 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:
- tsdown-dist-layout-in-tests — 100% identical, 0 lines differ
What it actually says
tsdown dist layout for test path mappings
When packages are built with tsdown, declaration outputs are emitted in the package dist/ root as .d.mts files (for example dist/types.d.mts), not under dist/exports/*.d.ts.
Rules
- In temporary
tsconfigfixtures used by tests, map package paths todist/*.d.mtsordist/*. - Do not assume
dist/exports/exists unless the package explicitly emits that structure. - Prefer wildcard mappings (
dist/*) for subpath imports that may include both.mjsand.d.mtsoutputs.
Why
- Prevents module resolution failures after tsup -> tsdown migrations.
- Keeps integration tests aligned with the actual package export artifact layout.
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.
- 3d ago First seen · 20 lines · 10 tokens per session scan A 98f163962792
tsdown-dist-layout-in-tests is a cursor rule published in the GitHub repository prisma/orm (47,606 stars, last pushed 4d ago), licensed Apache-2.0. It adds 10 tokens to every session and 187 once invoked, about $0.0001 per session on Opus 5. 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-hash-constructors
Use coreHash() and profileHash() constructors instead of 'as never' casts for branded hash types.
typed-contract-in-tests
Use typed Contract from fixtures in integration tests.
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
use-ast-factories
Use factory functions for creating AST nodes instead of manual object creation.
vitest-expect-typeof
The toMatchTypeOf() matcher has been deprecated in Vitest's expectTypeOf API.
test-mocking-patterns
Test-only type assertions and mocking patterns (avoid brittle mocks).