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/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/git-code-prep)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-code-prep"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-code-prep/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-code-prep"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-code-prep.svg" alt="Reviewed on agentmods" width="80" 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.02351 |
| Opus 5.5 | $0.00000 | $0.00940 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago 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
git
Git workflow — commit format, push policy, and PR process.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.