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/prisma-nextWrote 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/prisma-next/tsdown-dist-layout-in-tests)<a href="https://agentmods.dev/rules/prisma/prisma-next/tsdown-dist-layout-in-tests"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/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.
This is a copy
100% identical to tsdown-dist-layout-in-tests — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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/prisma-next (418 stars, last pushed 12d 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. It is 100% identical to tsdown-dist-layout-in-tests, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
use-ast-factories
Use factory functions for creating AST nodes instead of manual object creation.
test-mocking-patterns
Test-only type assertions and mocking patterns (avoid brittle mocks).
tsdown-dist-layout-in-tests
Use tsdown dist root paths in TS test mappings.
no-bare-casts
No bare as casts in production TypeScript. Use blindCast (value) from @internal/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.
sql-types-imports
Canonical import paths for SQL types.
type-extraction-from-contract
Extract TypeScript types from contract.d.ts and helpers.