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/arxdsilva/vaultWrote 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/arxdsilva/vault/git-commits)<a href="https://agentmods.dev/rules/arxdsilva/vault/git-commits"><img src="https://agentmods.dev/badge/rules/arxdsilva/vault/git-commits/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/arxdsilva/vault/git-commits"><img src="https://agentmods.dev/badge/rules/arxdsilva/vault/git-commits.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.01004 | $0.01004 |
| Opus 5.5 | $0.00402 | $0.00402 |
| Sonnet 5.5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
git-commits 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Practices
Commits are a human action. The AI must never run git commit, git add (to stage for a commit), or git commit --amend — even when the user says "commit this" or "commit your changes."
When commits are in scope, the AI may inspect the repo and prepare a commit for the human; the human runs the final git commands locally.
What the AI Must Never Do
- Run
git commitorgit commit --amend - Run
git addto stage files for a commit - Create commits to "save progress" or after finishing a task
- Create empty commits
- Push to the remote unless the user explicitly asks (see Push below)
If the user asks you to commit, decline the git command and instead offer a ready-to-run suggestion (message + git add / git commit commands they can copy).
What the AI May Do
- Run read-only inspection:
git status,git diff,git log - Draft a commit message and list which paths to stage
- Warn about secrets (
.env,credentials.json, tokens, keys) that must not be committed - Fix hook/lint issues in code when asked — the human commits after validation
Git Safety Protocol
When any git write command is in scope (e.g. push, branch ops), still follow:
- Never update git config (
git config, global or local) - Never run destructive or irreversible commands (
push --force,reset --hard, etc.) unless the user explicitly requests them - Never skip hooks (
--no-verify,--no-gpg-sign, etc.) unless the user explicitly requests it - Never force-push to
mainormaster; warn the user if they ask - Never use interactive git (
git add -i,git rebase -i)
Suggesting a Commit (human runs these)
When the user wants to commit, or work is ready to land, follow this sequence.
1. Inspect (run in parallel)
git status
git diff # staged and unstaged
git log -10 --oneline # match recent message style
Do not run extra exploration commands beyond these git commands.
2. Draft the 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 · 112 lines · 1,004 tokens per session scan A 88bc9c37d0cf
git-commits is a cursor rule published in the GitHub repository arxdsilva/vault (3 stars, last pushed 14d ago), licensed MIT. It adds 1,004 tokens to every session, about $0.0040 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
commit-message-english
Use English for git commit messages.
git-commits
Git commit and branch conventions.
no-ai-contributors
Never add AI tools as git authors or project contributors.
general
General rules for Claude Code when working on go-crypto-wallet.
git-commits
Git commit safety — commits are human-only; AI suggests, never executes.
commit-message-style
Generating properly formatted git commit message.