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/eastlondoner/vibe-toolsWrote 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/eastlondoner/vibe-tools/git-commit)<a href="https://agentmods.dev/rules/eastlondoner/vibe-tools/git-commit"><img src="https://agentmods.dev/badge/rules/eastlondoner/vibe-tools/git-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/eastlondoner/vibe-tools/git-commit"><img src="https://agentmods.dev/badge/rules/eastlondoner/vibe-tools/git-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.00012 | $0.00339 |
| Opus 5.5 | $0.00005 | $0.00136 |
| Sonnet 5.5 | $0.00002 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
git-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.
What it actually says
When making a commit run git status to see what the local changes are.
Don't worry about untracked files that you don't recognize. We often have a lot of local cruft that doesn't need to be tracked.
Make sure to add any new currently untracked files that you've introduced and if there are important looking files that might need to be tracked ask me about it.
Once you've got all the correct files being tracked check the diff between the current branch and main (ignoring untracked files) to fully understand what changes are in progress.
Check that ARCHITECTURE.md and ONBOARDING.md are up-to-date with the changes in progress. If they're not up-to-date then update those files, keeping consistency with the existing approach in those files, update them so that they are up to date with the changes in progress and the current state of the code in general. Make sure to read in the actual files at this stage to make sure that you get this right. Note in many cases for smaller or implementation detail changes you won't need to change these files, don't modify them unnecessarily.
Ensure that any new or changed functionality has test coverage including test coverage for failure and 'unhappy path' cases. If test coverage is missing and not trivial to add, write a report of the missing tests to a markdown file and then check with me.
Make sure that build and test are passing.
Remove any debug logging that's been left in the changes in progress. We often commit this accidentally so it's good to clean up, but only do this once tests are passing!
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 · 21 lines · 12 tokens per session scan A 256891fefcdd
git-commit is a cursor rule published in the GitHub repository eastlondoner/vibe-tools (4,820 stars, last pushed 1y ago), licensed MIT. It adds 12 tokens to every session and 339 once invoked, about $0.0000 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-30.
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.