import-validation

Rules for checking imports against a package architecture divided into domains, layers, and planes. They enforce which parts of the code may depend on one another.

In plain words
What is it for?
Use them to keep a large codebase organised and to validate package dependencies automatically.
Why use it?
They catch imports that point in the wrong direction or cross package boundaries that the project does not allow.

Cursor rule for Codex

Install

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.

agentmods
npx agentmods add rules/prisma/prisma-next/import-validation
Clone the repo
git clone --depth 1 https://github.com/prisma/prisma-next

Made for: Codex.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,073 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash 427f182db59e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

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.

.agents/rules/import-validation.mdc · 102 lines

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:

  1. Package configs map a glob to domain/layer/plane:
    { "glob": "packages/framework/core-plan/**", "domain": "framework", "layer": "core", "plane": "shared" }
    
  2. Layer order defines dependency direction per domain:
    { "layerOrder": { "sql": ["core", "authoring", "targets", "lanes", "runtime", "adapters"] } }
    
  3. Rules define allowed/denied patterns:
    { "rules": { "sameLayer": "allow", "downward": "allow", "upward": "deny",
      "crossDomain": "denyExceptFramework", "migrationToRuntime": "deny",
      "runtimeToMigration": "allowArtifactsOnly" } }
    
  4. Plane rules declare per-plane allow/forbid plus exceptions:
    { "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-lane may import sql-relational-core (both lanes):
    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';
    

Read the full file on GitHub · 102 lines

Changes

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.

  1. yesterday First seen · 102 lines · 0 tokens per session scan A 427f182db59e

Subscribe to this mod's changes

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.