no-git-commit-by-agent

no-git-commit-by-agent is a cursor rule for Cursor from Elumenotion/GuideAnts. It costs 156 tokens per session, scanned A, original, Apache-2.0.

A rule that keeps coding-agent commits under the user's control. A commit is a saved group of changes in a Git project.

In plain words
What is it for?
Use it to require agents to leave changes unstaged or staged for review, suggest a commit message, and hand the final commit or push command to the user.
Why use it?
It prevents an agent from silently creating commits or sending them to a remote repository.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to require agents to leave changes unstaged or staged for review, suggest a commit message, and hand the final commit or push command to the user.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/elumenotion/guideants/no-git-commit-by-agent
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Elumenotion/GuideAnts

Made for: Cursor.

Wrote 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.

agentmods badge for no-git-commit-by-agent

README.md
[![agentmods](https://agentmods.dev/badge/rules/elumenotion/guideants/no-git-commit-by-agent/github.svg)](https://agentmods.dev/rules/elumenotion/guideants/no-git-commit-by-agent)
Your own site
<a href="https://agentmods.dev/rules/elumenotion/guideants/no-git-commit-by-agent"><img src="https://agentmods.dev/badge/rules/elumenotion/guideants/no-git-commit-by-agent/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.

agentmods 80×15 button for no-git-commit-by-agent

Your own site · 80×15
<a href="https://agentmods.dev/rules/elumenotion/guideants/no-git-commit-by-agent"><img src="https://agentmods.dev/badge/rules/elumenotion/guideants/no-git-commit-by-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 156 This file is loaded in full into every session.
When invoked 156 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00156 $0.00156
Opus 5.5 $0.00062 $0.00062
Sonnet 5.5 $0.00031 $0.00031
Haiku 4.5 $0.00016 $0.00016

Measured 1mo ago against content hash c06ff8e9e88e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

no-git-commit-by-agent 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.

src/.cursor/rules/no-git-commit-by-agent.mdc · 14 lines

What it actually says

Commit Ownership

  • Never run git commit in any form.
  • Never run git commit --amend.
  • Never run git push unless the user explicitly asks in the current message (see git-branch-and-push-safety.mdc).
  • Stage files and propose a commit message when helpful, then stop and ask the user to run the commit.
  • If asked to commit, explain that commits are user-owned in this project and hand off the exact command/message for the user to run.
  • If asked to push, verify git branch -vv shows upstream origin/<same-branch>, not origin/main, before handing off the push command.
Changes

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.

  1. 1mo ago First seen · 14 lines · 156 tokens per session scan A c06ff8e9e88e

Subscribe to this mod's changes

no-git-commit-by-agent is a cursor rule published in the GitHub repository Elumenotion/GuideAnts (61 stars, last pushed 2d ago), licensed Apache-2.0. It adds 156 tokens to every session, about $0.0006 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.