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/cdbattags/aiWrote 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/cdbattags/ai/git-commit-confirmation)<a href="https://agentmods.dev/rules/cdbattags/ai/git-commit-confirmation"><img src="https://agentmods.dev/badge/rules/cdbattags/ai/git-commit-confirmation/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/cdbattags/ai/git-commit-confirmation"><img src="https://agentmods.dev/badge/rules/cdbattags/ai/git-commit-confirmation.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.00463 | $0.00463 |
| Opus 5.5 | $0.00185 | $0.00185 |
| Sonnet 5.5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
git-commit-confirmation 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.
What it actually says
Git Commit Confirmation
ABSOLUTE RULE — NO EXCEPTIONS
NEVER run git commit without explicit user approval.
STOP. ASK. WAIT. Only commit after the user says "yes" or "commit".
Mandatory Workflow
When changes are ready to commit:
- Make the changes — edit, create, or delete files as requested
- Show what changed — optionally show
git statusandgit diff - Draft commit message — prepare a clear, descriptive commit message
- STOP — do NOT proceed without user approval
- Ask explicitly — "Ready to commit these changes?"
- Wait for response — do not assume, do not proceed
- Only after "yes" — user must say "yes", "commit", "go ahead", etc.
- Then and only then commit
Pattern to Follow
End your response with:
I've made the following changes:
- [list changes]
Proposed commit message:
---
[commit message]
---
Ready to commit these changes?
Then stop. Wait. Do not commit until user responds.
When NOT to Commit
Do not commit if the user:
- Just asked to "fix" or "change" something
- Reported an error or issue
- Has not explicitly said "commit" or "yes, commit"
When TO Commit
Only commit if the user explicitly:
- Says "commit this"
- Says "yes" to a commit confirmation prompt
- Asks to "commit the changes"
- Says "create a commit with message X"
No Exceptions
Do NOT commit even if:
- The change is small or trivial
- The user approved previous commits in this conversation
- You think the user "obviously" wants it committed
- The changes are "ready" or it's the end of a task
Every single commit requires explicit approval for that specific commit.
Applies To
All git commit operations: git commit, git commit -m,
git commit --amend, git commit -a.
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 · 77 lines · 463 tokens per session scan A 13c8d5275973
git-commit-confirmation is a cursor rule published in the GitHub repository cdbattags/ai (5 stars, last pushed 7mo ago), licensed MIT. It adds 463 tokens to every session, about $0.0019 per session on Opus 5.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
no-auto-commit
Never commit or push without explicit user instruction.
git-workflow
Git workflow: commits, branches, PRs, history management.
git
A set of rules for using Git, a tool for tracking code changes. It covers commits, branches, and general version-control principles.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.
conventional-commits
Conventional Commits format enforced by pre-commit hooks.
pre-commit-lint-format
Run lint and format checks before every git commit.