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.
git clone --depth 1 https://github.com/prisma/prisma-nextWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/prisma/prisma-next/directory-layout)<a href="https://agentmods.dev/rules/prisma/prisma-next/directory-layout"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/directory-layout/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/prisma/prisma-next/directory-layout"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/directory-layout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01075 |
| Opus 5.5 | $0.00000 | $0.00430 |
| Sonnet 5.5 | $0.00000 | $0.00215 |
| Haiku 4.5 | $0.00000 | $0.00108 |
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 1mo 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
86% identical to directory-layout — 12 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 — 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.
- 1mo ago First seen · 95 lines · 0 tokens per session scan A 9108ed10f722
directory-layout is a cursor rule published in the GitHub repository prisma/prisma-next (414 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,075 tokens. A static security scan graded it A with 0 findings. It is 86% identical to directory-layout, differing in 12 lines, and is treated as a copy.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.