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/git-code-prepgit 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.00000 | $0.02351 |
| Opus 5 | $0.00000 | $0.01175 |
| Sonnet 5 | $0.00000 | $0.00470 |
| Haiku 4.5 | $0.00000 | $0.00235 |
Grade A, and why
git-code-prep 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.
How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Code Preparation Guide
This prompt handles the preparation phase of git workflow - analyzing changes, updating documentation, and planning commits before actual commit execution.
🎯 PREPARATION OBJECTIVES:
- ANALYZE code changes and determine commit strategy
- UPDATE documentation including changelogs and project docs
- PLAN commit structure and messaging strategy
- RUN initial quality checks and precommit hooks
- STAGE appropriate files for commit execution
📋 PREPARATION PROCESS:
STEP 1: Change Analysis & Assessment
Comprehensive Change Review:
- Analyze scope of changes - Review all modified, added, and deleted files
- Categorize changes by type - Features, bug fixes, refactoring, documentation, etc.
- Identify breaking changes - API modifications, interface changes, deprecated features
- Assess user impact - How changes affect functionality and user experience
- Determine version impact - Major, minor, or patch version bump needed
Change Impact Assessment:
- Files modified - List all changed files with brief description of changes
- Dependencies affected - External packages, internal modules, configuration files
- Database implications - Schema changes, migration requirements, data impact
- API surface changes - New endpoints, modified responses, deprecated routes
- Performance implications - Bundle size impact, runtime performance changes
STEP 2: Commit Strategy Planning
Commit Structure Decision:
- Single commit criteria - Small, cohesive changes related to single concern
- Multiple commit criteria - Mixed change types, large features, independent fixes
- Logical grouping - Group related changes into coherent commit units
- Dependency ordering - Plan commit sequence to maintain working state
Commit Planning Matrix:
Commit 1: [Type] - [Brief description]
├── Files: [list of files]
├── Scope: [what this commit covers]
└── Message: [planned commit message]
Commit 2: [Type] - [Brief description]
├── Files: [list of files]
├── Scope: [what this commit covers]
└── Message: [planned commit message]
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.
- yesterday First seen · 298 lines · 0 tokens per session scan A 439dbd59da60
git-code-prep is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,351 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-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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.