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.
npx agentmods add rules/prisma/prisma-next/multi-plane-entrypointsgit clone --depth 1 https://github.com/prisma/prisma-nextWhat 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 | $0.00000 | $0.00605 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
multi-plane-entrypoints 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 2d 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
95% identical to multi-plane-entrypoints — 2 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi‑Plane Entrypoints in a Single Package
Sometimes a single installable package must serve both migration and runtime planes with distinct entrypoints (e.g., adapter /control for control plane and /runtime for execution) while sharing a core implementation. This rule encodes how to do that without violating plane boundaries.
Pattern
- Keep one NPM package (e.g.,
@prisma-next/adapter-postgres). - Split sources by plane inside the package:
src/core/**— shared plane onlysrc/exports/control.ts— migration plane entrypoint (control plane)src/exports/runtime.ts— runtime plane entrypoint
- Export entrypoints from
package.json:
{
"exports": {
"./adapter": { "types": "./dist/exports/adapter.d.ts", "import": "./dist/exports/adapter.js" },
"./control": { "types": "./dist/exports/control.d.ts", "import": "./dist/exports/control.js" },
"./runtime": { "types": "./dist/exports/runtime.d.ts", "import": "./dist/exports/runtime.js" }
}
}
Architecture Mapping
Register subpaths as separate globs in architecture.config.json to map planes:
{ "glob": "packages/targets/postgres-adapter/src/core/**", "domain": "targets", "layer": "adapters", "plane": "shared" }
{ "glob": "packages/targets/postgres-adapter/src/exports/control.ts", "domain": "targets", "layer": "adapters", "plane": "migration" }
{ "glob": "packages/targets/postgres-adapter/src/exports/runtime.ts", "domain": "targets", "layer": "adapters", "plane": "runtime" }
This lets dependency guards treat a single package as three plane‑scoped module groups, so imports remain plane‑safe.
Do’s and Don’ts
- Do keep
src/core/**free of migration/runtime imports; depend only on shared‑plane packages. - Do import control plane/tooling only from
src/exports/control.ts. - Do import runtime/driver only from
src/exports/runtime.ts. - Don't add plane‑crossing imports inside
src/core/**. - Don't export plane‑specific files via the wrong entrypoint.
- Naming convention: Migration plane entrypoints use
control.ts(notcli.ts) and export as./control(not./cli).
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.
- 2d ago First seen · 55 lines · 0 tokens per session scan A e09efbb62ae6
multi-plane-entrypoints is a cursor rule published in the GitHub repository prisma/prisma-next (421 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 605 tokens. A static security scan graded it A with 0 findings. It is 95% identical to multi-plane-entrypoints, differing in 2 lines, and is treated as a copy.
Other cursor rules, from other repositories
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
directory-layout
Directory layout rules for SQL family vs concrete targets.
family-instance-domain-actions
Family instance domain action implementation patterns.
import-validation
Import validation and package layering rules.