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-commit)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-code-commit"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-code-commit/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-commit"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-code-commit.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.02240 |
| Opus 5.5 | $0.00000 | $0.00896 |
| Sonnet 5.5 | $0.00000 | $0.00448 |
| Haiku 4.5 | $0.00000 | $0.00224 |
Grade A, and why
git-code-commit 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Code Commit Execution Guide
This prompt handles the commit execution phase - final validation of prepared changes and clean commit execution with proper messaging.
🎯 COMMIT EXECUTION OBJECTIVES:
- PERFORM final validation of staged changes and documentation
- EXECUTE commits following planned strategy from preparation phase
- VERIFY commit integrity and proper formatting
- HANDLE multiple commits with appropriate sequencing
- CONFIRM repository state after commit completion
📋 COMMIT EXECUTION PROCESS:
STEP 1: Pre-Commit Final Validation
Staged Changes Review:
# Review what's about to be committed
git status # Overall repository status
git diff --staged # Review all staged changes
git diff --staged --stat # Summary of staged file changes
Final Quality Checks:
# Run final validation suite
npm run precommit # Project-specific precommit hooks
npm run lint --staged # Lint only staged files
npm run type-check # TypeScript validation
npm run test:quick # Quick test suite (if available)
Pre-Commit Validation Checklist:
- All required files staged - Documentation, code, configuration
- No unintended files staged - No temporary files, logs, or secrets
- Precommit hooks pass - All automated checks succeed
- Commit messages prepared - Clear, conventional format planned
- Documentation complete - Changelog, README, API docs updated
STEP 2: Commit Message Validation
Conventional Commit Format Verification:
<type>(<scope>): <subject>
<body>
<footer>
Commit Message Quality Standards:
- Subject line - ≤50 characters, imperative mood, no period
- Body - Wrapped at 72 characters, explains what and why
- Footer - References issues, breaking changes, co-authors
- Type accuracy - Matches actual change type (feat, fix, docs, etc.)
- Scope relevance - Accurately represents affected area
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 · 295 lines · 0 tokens per session scan A 3488f189c171
git-code-commit 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,240 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.