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/test-packages)<a href="https://agentmods.dev/rules/prisma/prisma-next/test-packages"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/test-packages.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.00005 | $0.00021 |
| Opus 5 | $0.00003 | $0.00010 |
| Sonnet 5 | $0.00001 | $0.00004 |
| Haiku 4.5 | $0.00001 | $0.00002 |
Grade A, and why
test-packages 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 test-packages — 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
pnpm test:packages
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 · 8 lines · 5 tokens per session scan A 8ff2e99e445b
test-packages is a cursor rule published in the GitHub repository prisma/prisma-next (418 stars, last pushed 13d ago), licensed Apache-2.0. It adds 5 tokens to every session and 21 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to test-packages, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
test-database-limitations
Test databases created via withDevDatabase() from @repo/test-utils use pglite (an in-memory PostgreSQL implementation via @prisma/dev). Pglite does not support PostgreSQL extensions like pgvector, pgtrgm, etc.
test-file-organization
Test file organization and splitting guidelines.
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.
running-tests
How to run tests, check for failures, and rerun specific failing tests — use the :agent variants of slow commands.
sql-orm-client-whole-shape-assertions
Prefer whole-result-shape assertions with explicit select projections in sql-orm-client tests.