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/moving-packagesgit 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.00943 |
| Opus 5 | $0.00000 | $0.00472 |
| Sonnet 5 | $0.00000 | $0.00189 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
moving-packages 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:
- moving-packages — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Moving Packages
When moving packages to new locations, you must update all relative paths that reference root-level files or other packages.
Relative Path Calculation
Key Principle: Count the directory depth from the package to the root, then use that many ../ segments.
Formula: Count the directory depth from package to root (note: numbered prefixes like 1-framework count as one directory):
- From
packages/1-framework/1-core/shared/plan/to root = 5 levels up (../../../../../) - From
packages/2-sql/3-tooling/emitter/to root = 4 levels up (../../../../) - From
packages/3-targets/6-adapters/postgres/to root = 4 levels up (../../../../) - From
packages/3-extensions/pgvector/to root = 3 levels up (../../../)
Common Paths to Update
- Test files - Paths to other packages:
- Extension pack manifests (e.g.,
packages/sql/runtime/adapters/postgres/packs/manifest.json) - Fixture paths
- Import paths in test utilities
- Extension pack manifests (e.g.,
Examples
Moving from packages/ to test/
Before (from packages/integration-tests/test/):
const packs = loadExtensionPacks(join(__dirname, '../../sql/runtime/adapters/postgres'), []);
// Resolves to: packages/sql/runtime/adapters/postgres
After (from test/integration/test/):
const packs = loadExtensionPacks(join(__dirname, '../../../packages/3-targets/6-adapters/postgres'), []);
// Resolves to: packages/3-targets/6-adapters/postgres
Why? From test/integration/test/:
../→test/integration/../../→test/../../../→ root../../../packages/3-targets/→packages/3-targets/
Checklist When Moving Packages
- Update test files - Paths to other packages, fixtures, manifests
- Update
pnpm-workspace.yaml- Add/remove package globs if needed - Update
architecture.config.json- Add/remove package entries- For multi-plane packages, add separate globs for each plane (see
.cursor/rules/multi-plane-packages.mdc)
- For multi-plane packages, add separate globs for each plane (see
- Update
tsconfig.base.json- Update project references - Update
dependency-cruiser.config.mjs- Update exclude patterns if needed - Update CI workflows - Update any hardcoded paths
- Update documentation - READMEs, AGENTS.md, etc.
- Update relative paths in source files - Manifest paths, import paths, etc.
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 · 97 lines · 0 tokens per session scan A f8071cf50f6f
moving-packages 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 943 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.