import-validation

A rule for checking imports against the repository's domain, layer, and plane structure. Dependency direction means lower-level code can be used by higher-level code, but not the reverse.

In plain words
What is it for?
Use it when adding imports or packages, configuring dependency checks, and verifying that framework and target-family code follow the allowed layering.
Why use it?
It catches dependencies that cross architectural boundaries or point upward toward code that should depend on them.

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/orm/import-validation
Clone the repo
git clone --depth 1 https://github.com/prisma/orm

Made for: Codex.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,067 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.01067
Opus 5 $0.00000 $0.00534
Sonnet 5 $0.00000 $0.00213
Haiku 4.5 $0.00000 $0.00107

Measured 2d ago against content hash 8bdfedb5e69d, 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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.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 '@internal/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 '@internal/plan';
    // ❌ core importing lanes
    import { sql } from '@internal/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. 2d ago First seen · 102 lines · 0 tokens per session scan A 8bdfedb5e69d

Subscribe to this mod's changes

import-validation is a cursor rule published in the GitHub repository prisma/orm (47,579 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,067 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.