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/bayesimpact/bayes-platformWrote 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/bayesimpact/bayes-platform/no-autonomous-git-commit-push)<a href="https://agentmods.dev/rules/bayesimpact/bayes-platform/no-autonomous-git-commit-push"><img src="https://agentmods.dev/badge/rules/bayesimpact/bayes-platform/no-autonomous-git-commit-push/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/bayesimpact/bayes-platform/no-autonomous-git-commit-push"><img src="https://agentmods.dev/badge/rules/bayesimpact/bayes-platform/no-autonomous-git-commit-push.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.00155 | $0.00155 |
| Opus 5 | $0.00077 | $0.00077 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
no-autonomous-git-commit-push 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 2d 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
No Autonomous Git Commits or Pushes
NEVER run git commit or git push (on any branch or worktree) unless the user explicitly asks for it in their message.
- Fixing a bug, a failing CI check, or completing a task is NOT implicit permission to commit or push.
- When a fix requires a commit/push to take effect (e.g. CI runs on the remote branch), stage or prepare the changes, then stop and tell the user what to commit and push.
- Instead of committing, end the response with the usual suggested commit message (
💬 Git: ...) and let the user run the git commands themselves.
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.
- 2d ago First seen · 13 lines · 155 tokens per session scan A 9fad8d74f643
no-autonomous-git-commit-push is a cursor rule published in the GitHub repository bayesimpact/bayes-platform (18 stars, last pushed yesterday), licensed MIT. It adds 155 tokens to every session, about $0.0008 per session on Opus 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-14.
Other cursor rules, from other repositories
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
roslyn-mcp-version-bump
Auto-bump Version after successful MCP self-build and reload.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
git-commits
description: "Reference and apply the git commits skill for Conventional Commit formatting and pre-push checks." alwaysApply: true.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.