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/CiscoDevNet/essentialsWrote 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/ciscodevnet/essentials/git-commits)<a href="https://agentmods.dev/rules/ciscodevnet/essentials/git-commits"><img src="https://agentmods.dev/badge/rules/ciscodevnet/essentials/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/ciscodevnet/essentials/git-commits"><img src="https://agentmods.dev/badge/rules/ciscodevnet/essentials/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.00517 | $0.00517 |
| Opus 5.5 | $0.00207 | $0.00207 |
| Sonnet 5.5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
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 20d 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 Commits
Commit messages and pull requests contain only what the user asked for. Never add
Co-authored-by: trailers or any other agent attribution.
Cursor appends a Co-authored-by: Cursor trailer to every agent git commit, whatever the
settings or rules say. The strip-cursor-coauthor commit-msg hook removes it before the
commit is created, so commit normally and let the hooks run.
Committing
-
Once per checkout, make sure the commit-msg hook is installed. A plain install covers every stage listed in
default_install_hook_types:test -x "$(git rev-parse --git-path hooks)/commit-msg" || uv run pre-commit install -
Commit with
git commit. Never pass--no-verify: it skips the hook that removes the trailer, along with the message checks. -
Verify with
git log -1 --format=full. If the trailer is still there, the hook did not run: install it (step 1), thengit commit --amend --no-editwhile the commit is unpushed.
Fallback: no hooks
If installing the hooks is not an option, build the commit with git commit-tree, which
Cursor leaves alone. It skips every hook too, so run them yourself first:
uv run pre-commit run --files $(git diff --cached --name-only)
uv run pre-commit run --hook-stage commit-msg --commit-msg-filename /tmp/commit-msg
old=$(git rev-parse HEAD)
new=$(git commit-tree "$(git write-tree)" -p "$old" < /tmp/commit-msg)
git update-ref "refs/heads/$(git branch --show-current)" "$new" "$old"
Passing the old tip makes update-ref fail if the branch moved in the meantime.
Pull requests
- Never append
Made with Cursor,Made with [Cursor](https://cursor.com), or similar attribution to PR titles or bodies. - PR descriptions contain only Summary and Test plan, or what the user asked for.
- After
gh pr createorgh pr edit, checkgh pr view <number> --json bodyand remove any injected footer.
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.
- 20d ago First seen · 51 lines · 517 tokens per session scan A f2f654e44fe6
git-commits is a cursor rule published in the GitHub repository CiscoDevNet/essentials (7 stars, last pushed 9d ago), licensed Apache-2.0. It adds 517 tokens to every session, about $0.0021 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-09-25.
Other cursor rules, from other repositories
review-scope-overrides
Honor explicitly provided base branches in review artifacts.
speckit_speckit.git.commit
description: Proxy for the speckit.git.commit workflow globs.
ai-coding
A set of rules for AI-assisted coding, including Chinese-language communication and comments, commit-message formatting, small changes, and human review of sensitive code.
no-git-commit-by-agent
Keep git commits user-owned.
version-management
Automatically commit and push changes after completing any feature, bug fix, or significant addition.
release-ts-sdk
Release @aptos-labs/ts-sdk or @aptos-labs/confidential-asset — version bump, changelog stamp, release PR, then tag + GitHub Release that triggers NPM publish.