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/oakensoul/nextjs-cursor-prompts/code-change-refactorgit clone --depth 1 https://github.com/oakensoul/nextjs-cursor-promptsWhat 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.00023 | $0.01997 |
| Opus 5 | $0.00012 | $0.00999 |
| Sonnet 5 | $0.00005 | $0.00399 |
| Haiku 4.5 | $0.00002 | $0.00200 |
Grade A, and why
code-change-refactor 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Refactoring Rule
This rule applies when refactoring existing code to improve quality, adopt new patterns, or integrate with newly created functionality.
🎯 REFACTORING PRINCIPLES:
- PRESERVE FUNCTIONALITY - External behavior must remain identical
- IMPROVE INCREMENTALLY - Make steady, measurable improvements
- MAINTAIN TESTABILITY - Keep or improve test coverage
- FOLLOW EXISTING PATTERNS - Adopt established project conventions
- REDUCE COMPLEXITY - Simplify without breaking existing contracts
🚫 FORBIDDEN ACTIONS:
- DO NOT change external APIs or public interfaces without explicit approval
- DO NOT break existing functionality or user-facing behavior
- DO NOT refactor without tests - ensure test coverage exists or create it first
- DO NOT make massive changes in a single refactoring session
- DO NOT introduce new dependencies unless necessary for the improvement
- DO NOT refactor multiple concerns simultaneously (separate data flow from UI changes)
- DO NOT remove error handling or validation without replacement
- DO NOT change business logic while refactoring structure
✅ ENCOURAGED ACTIONS:
- EXTRACT reusable components and utilities from duplicated code
- CONSOLIDATE similar patterns into consistent implementations
- IMPROVE naming to be more descriptive and intention-revealing
- ENHANCE error handling and edge case management
- OPTIMIZE data flow and state management patterns
- STRENGTHEN type safety and validation
- SIMPLIFY complex functions by breaking them into smaller, focused units
- ADOPT project standards and established patterns
🏗️ BUILT-IN ARCHITECTURAL REQUIREMENTS:
- Follow NextJS App Router patterns - use app directory structure, proper layouts
- Maintain server/client boundaries - use 'use client' appropriately, avoid server-side DOM
- Implement proper error boundaries - handle errors at appropriate component levels
- Follow established folder structure - components, utils, hooks, types in standard locations
- Use consistent naming conventions - kebab-case files, PascalCase components
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 · 217 lines · 23 tokens per session scan A 43f486126f8b
code-change-refactor is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It adds 23 tokens to every session and 1,997 once invoked, about $0.0001 per session on Opus 5. 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-31.
Other cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.