What is modular-refactoring-patterns?

Patterns for splitting a large, single-file implementation into smaller modules while keeping its public interface unchanged.

Use it when breaking up a large file: move pure helper functions first, then types, while preserving the existing public API.

It makes code easier to understand and helps avoid import cycles, where files depend on each other in a loop.

modular-refactoring-patterns — Cursor rule by prisma

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/modular-refactoring-patterns

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 142 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00142
Opus 5	$0.00000	$0.00071
Sonnet 5	$0.00000	$0.00028
Haiku 4.5	$0.00000	$0.00014

Measured yesterday against content hash a66662e6b77d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

modular-refactoring-patterns 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 yesterday.

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:

modular-refactoring-patterns — 100% identical, 0 lines differ

.agents/rules/modular-refactoring-patterns.mdc · 21 lines

What it actually says