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-minimalgit clone --depth 1 https://github.com/oakensoul/nextjs-cursor-promptsWrote 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/oakensoul/nextjs-cursor-prompts/code-change-minimal)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/code-change-minimal"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/code-change-minimal.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 | $0.00022 | $0.01432 |
| Opus 5 | $0.00011 | $0.00716 |
| Sonnet 5 | $0.00004 | $0.00286 |
| Haiku 4.5 | $0.00002 | $0.00143 |
Grade A, and why
code-change-minimal 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 5d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
title: Minimal Change Hook description: Ensures focused, minimal changes that respect existing codebase and avoid unnecessary rewrites or assumptions tags: [prompt, minimal-change, focused-updates, code-preservation, incremental-changes] version: 1.0.0 lastUpdated: 2025-06-02 usage: Use as a prefix when making small updates or targeted changes to existing code audience: [claude, ai-assistants] scope: [code-preservation, minimal-changes, incremental-updates, existing-codebase-respect]
Minimal Code Change Rule
This rule applies to ANY development task. When referenced, you must follow these constraints regardless of the primary prompt.
🚫 FORBIDDEN ACTIONS:
- DO NOT rewrite existing working code unless explicitly required for the task
- DO NOT assume files don't exist - always analyze the current codebase first
- DO NOT change file structure or move files unless specifically requested
- DO NOT modify unrelated code or files outside the task scope
- DO NOT add new dependencies unless absolutely necessary for the task
- DO NOT change existing patterns or architecture without explicit need
- DO NOT refactor for the sake of refactoring - preserve working patterns
- DO NOT over-engineer simple requests into complex solutions
✅ REQUIRED ACTIONS:
- ANALYZE the existing codebase thoroughly before any changes
- PRESERVE existing patterns and coding styles
- MAKE MINIMAL changes that accomplish the specific task
- USE existing utilities and helper functions where possible
- MAINTAIN consistency with current codebase architecture
- ASK for clarification if the task scope is ambiguous
- VERIFY file locations and existing implementations first
🔒 BUILT-IN SECURITY REQUIREMENTS:
- Validate all inputs - sanitize user data and API parameters
- Authenticate protected actions - verify user permissions before execution
- Use secure defaults - HTTPS, secure cookies, proper CORS settings
- Log security events - track authentication failures and suspicious activity
- Escape output - prevent XSS in rendered content
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.
- 5d ago First seen · 160 lines · 22 tokens per session scan A 9ccd305d5730
code-change-minimal is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It adds 22 tokens to every session and 1,432 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.
family-instance-domain-actions
Family instance domain action implementation patterns.
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.