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/import-validationgit 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.01073 |
| Opus 5 | $0.00000 | $0.00536 |
| Sonnet 5 | $0.00000 | $0.00215 |
| Haiku 4.5 | $0.00000 | $0.00107 |
Grade A, and why
import-validation 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 yesterday.
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 import-validation — 6 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Import Validation
The repo uses a domain/layer/plane package layering architecture with unidirectional dependencies
enforced by Dependency Cruiser, driven by data from architecture.config.json.
Domain/Layer/Plane Structure
Packages are organized by:
- Domains: framework (target-agnostic) and target families (sql, document, etc.).
- Layers: dependencies flow inward (toward core) within a domain —
core → authoring → targets → lanes → runtime → adapters. - Planes: migration (authoring, tooling, targets), runtime (lanes, runtime, adapters), and shared (cross-plane code and prebuilt artifacts safe for both).
Configuration (architecture.config.json)
dependency-cruiser.config.mjs reads data-driven config:
- Package configs map a glob to domain/layer/plane:
{ "glob": "packages/framework/core-plan/**", "domain": "framework", "layer": "core", "plane": "shared" } - Layer order defines dependency direction per domain:
{ "layerOrder": { "sql": ["core", "authoring", "targets", "lanes", "runtime", "adapters"] } } - Rules define allowed/denied patterns:
{ "rules": { "sameLayer": "allow", "downward": "allow", "upward": "deny", "crossDomain": "denyExceptFramework", "migrationToRuntime": "deny", "runtimeToMigration": "allowArtifactsOnly" } } - Plane rules declare per-plane
allow/forbidplusexceptions:{ "planeRules": { "shared": { "allow": ["shared"], "forbid": ["migration", "runtime"], "exceptions": [] }, "migration": { "allow": ["shared", "migration"], "forbid": ["runtime"], "exceptions": [] }, "runtime": { "allow": ["shared", "runtime"], "forbid": ["migration"], "exceptions": [] } } }
Rules
- Same-layer imports allowed — e.g.
orm-lanemay importsql-relational-core(bothlanes):import { schema } from '@prisma-next/sql-relational-core/schema'; - Cross-layer: import only from inner layers (closer to core). Outer layers cannot be imported
by inner ones:
// ✅ lanes importing core import { planInvalid } from '@prisma-next/plan'; // ❌ core importing lanes import { sql } from '@prisma-next/sql-lane';
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.
- yesterday First seen · 102 lines · 0 tokens per session scan A 427f182db59e
import-validation 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 1,073 tokens. A static security scan graded it A with 0 findings. It is 100% identical to import-validation, differing in 6 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.