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/running-tests)<a href="https://agentmods.dev/rules/prisma/prisma-next/running-tests"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/running-tests/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/prisma-next/running-tests"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/running-tests.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.00899 | $0.00899 |
| Opus 5.5 | $0.00360 | $0.00360 |
| Sonnet 5.5 | $0.00180 | $0.00180 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
running-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 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.
This is a copy
100% identical to running-tests — 16 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
How to run tests, check for failures, and get specific failures
1. Run a test suite
Each slow command has an :agent variant. The first line of its output prints the exact log path:
$ pnpm test:packages:agent
log: wip/test-packages.20260615-190441.32317.log
The full output goes to that file. The exit code is written to a sibling .exit file (same path with .log → .exit). Use the path printed by the command — don't guess one. Every run gets its own timestamped path, so history is preserved automatically. Contents of wip/ are gitignored.
Each :agent run has a hard timeout (default 5 minutes, override with AGENT_CMD_TIMEOUT_SECONDS — bump it for a legitimately long suite). If the run hangs — e.g. vitest freezes after printing its summary — the child process group is killed and the .exit file records 124 rather than blocking forever.
| Command | Purpose |
|---|---|
pnpm test:packages:agent |
Unit tests for every package |
pnpm test:integration:agent |
Integration suite (PGlite + mongodb-memory-server) |
pnpm test:e2e:agent |
End-to-end suite |
pnpm build:agent |
Build every package (turbo) |
pnpm typecheck:agent |
Typecheck every package (turbo, cached) |
pnpm lint:agent |
Biome lint |
pnpm lint:deps:agent |
Dependency-layering check |
pnpm fixtures:check:agent |
Regenerate fixtures and diff them |
2. Run one package's tests
pnpm --filter @prisma-next/cli test
Runs only that package's own test script — seconds, not minutes. Output goes to your terminal; no capture needed.
3. Rerun a specific failing test
By file:
pnpm --filter @prisma-next/cli test test/commands/migration-list-json-golden.test.ts
By test name within a file (vitest's -t filter):
pnpm --filter @prisma-next/cli test test/commands/migration-list-json-golden.test.ts -t "pins head ref decoration"
4. Find specific failures in the captured output
Use the log path the :agent command printed (the shell exit status tells you pass/fail; the .exit sibling file records the same number). If non-zero, list failing files and assertions:
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 · 76 lines · 899 tokens per session scan A ce2408f6decc
running-tests is a cursor rule published in the GitHub repository prisma/prisma-next (412 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 899 tokens to every session, about $0.0036 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to running-tests, differing in 16 lines, and is treated as a copy.
Other cursor rules, from other repositories
300-testing
Comprehensive testing guide covering unit, integration, E2E, test frameworks, patterns, and CI/CD integration.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
testing
Cursor rule "testing" from andersonlemesc/Oryntra, covering testes oryntra, laravel (pest), python (pytest), contract tests (laravel ↔ python) and browser/e2e.
30-testing
Convenciones de testing, cobertura mínima, tipos de tests, mocks.
tester
Tester role - Unit, E2E, and visual regression testing.
go-test
Rules for writing and modifying test files (test.go) in go-crypto-wallet.