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/orm/directory-layoutgit clone --depth 1 https://github.com/prisma/ormWhat 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.01063 |
| Opus 5 | $0.00000 | $0.00531 |
| Sonnet 5 | $0.00000 | $0.00213 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
directory-layout 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- directory-layout — 86% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directory Layout — Numbered Prefixes, Domains, Layers, and Planes
The repository uses numbered prefixes in directory names to reflect the architecture hierarchy and dependency direction.
Directory Structure
packages/
1-framework/ # Domain 1: Framework (target-agnostic)
1-core/ # Layer 1: Core
shared/ # Plane: Shared
contract/
plan/
operations/
migration/ # Plane: Migration
control-plane/
runtime/ # Plane: Runtime
execution-plane/
2-authoring/ # Layer 2: Authoring
3-tooling/ # Layer 3: Tooling
4-runtime-executor/ # Layer 4: Runtime Executor
2-document/ # Domain 2: Document (placeholder)
2-sql/ # Domain 2: SQL family
1-core/ # Layer 1: Core
2-authoring/ # Layer 2: Authoring
3-tooling/ # Layer 3: Tooling
4-lanes/ # Layer 4: Lanes
5-runtime/ # Layer 5: Runtime
3-extensions/ # Domain 3: Extensions
pgvector/
3-targets/ # Domain 3: Targets
3-targets/ # Layer 3: Target descriptors
postgres/
6-adapters/ # Layer 6: Adapters
postgres/
7-drivers/ # Layer 7: Drivers
postgres/
Numbered Prefix Rules
-
Domain numbers: Lower domain numbers can be imported by higher ones
- Domain 1 (framework) can be imported by domains 2 and 3
- Domain 2 (sql, document) cannot import from each other
- Domain 3 (targets, extensions) can import from domains 1 and 2
-
Layer numbers: Lower layer numbers can be imported by higher ones
- Within a domain, layer 1 (core) can be imported by layers 2, 3, 4, etc.
- Within a domain, layer 4 cannot import from layer 5
-
Planes: Appear as subdirectories only when needed
- Shared plane: can be imported by both migration and runtime
- Migration plane: cannot import from runtime
- Runtime plane: cannot import from migration (except artifacts)
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 · 95 lines · 0 tokens per session scan A acf969f71fb8
directory-layout 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,063 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.
Other cursor rules, from other repositories
config-validation-and-normalization
Patterns for config validation and normalization using Arktype.
contract-space-package-layout
On-disk layout for packages that expose a contract space (extensions, internal monorepo packages, aggregate-root apps).
cli-package-exports
CLI package export patterns and import conventions.
resolving-cyclic-dependencies
How to resolve cyclic dependencies when moving types or refactoring packages.
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values. Enforced by lint:framework-vocabulary.
review-scope-overrides
Honor explicitly provided base branches in review artifacts.