Prisma ORM is a Node.js and TypeScript database toolkit that lets applications work with databases through a programming interface instead of writing every query directly in SQL. Developers use it with databases including PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB, and CockroachDB. The catalogue add-ons provide agent rules, skills, hooks, agents, and other workflows for using Prisma.
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/ormWrote 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/orm/resolving-cyclic-dependencies)<a href="https://agentmods.dev/rules/prisma/orm/resolving-cyclic-dependencies"><img src="https://agentmods.dev/badge/rules/prisma/orm/resolving-cyclic-dependencies.svg" alt="Measured on agentmods" 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.00559 |
| Opus 5 | $0.00000 | $0.00280 |
| Sonnet 5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
resolving-cyclic-dependencies 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolving Cyclic Dependencies
Overview
When resolving dependency violations by moving types or refactoring packages, always check for unused dependencies that might create cycles. Cyclic dependencies can be broken by removing unused dependencies rather than restructuring code.
The Problem
When moving types to resolve dependency violations, you may discover that the target package already depends on the source package, creating a cycle:
Package A → Package B (needs types)
Package B → Package A (unused dependency)
The Solution
Before restructuring code, check if the cycle can be broken by removing unused dependencies:
- Check for unused dependencies: Use
grepto verify if Package B actually imports anything from Package A - Remove unused dependencies: If Package B doesn't use Package A, remove it from
package.json - Verify: Run
pnpm installandpnpm typecheckto ensure nothing breaks
Pattern
✅ CORRECT: Remove unused dependency to break cycle
# Check if package actually uses the dependency
grep -r "@internal/package-a" packages/framework/core-package-b/src
# If no matches, remove from package.json
# Then verify
pnpm install
pnpm --filter @internal/package-b typecheck
❌ WRONG: Restructure code when unused dependency exists
// Don't restructure types or create workarounds
// when the cycle can be broken by removing unused dependencies
Example
When moving TypesImportSpec from @internal/emitter to @internal/contract:
-
Discovered cycle:
@internal/contract→@internal/operations(needsOperationRegistry)@internal/operations→@internal/contract(unused dependency)
-
Verified unused:
grepshowed@internal/operationsdoesn't import from@internal/contract -
Removed dependency: Removed
@internal/contractfrom@internal/operations/package.json -
Verified fix:
pnpm installand typechecks passed
When to Use This Pattern
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.
- 3d ago First seen · 75 lines · 0 tokens per session scan A 7a8f40f17913
resolving-cyclic-dependencies is a cursor rule published in the GitHub repository prisma/orm (47,608 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 559 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-09-03.
Other cursor rules, from other repositories
resolving-cyclic-dependencies
How to resolve cyclic dependencies when moving types or refactoring packages.
lint-deps
Validate package layering and import rules.
contract-space-package-layout
On-disk layout for packages that expose a contract space (extensions, internal monorepo packages, aggregate-root apps).
sql-types-imports
Canonical import paths for SQL types.
cli-package-exports
CLI package export patterns and import conventions.
typescript-patterns
TypeScript and architecture patterns for this codebase.