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/quinnjr/google-mcpWrote 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/quinnjr/google-mcp/auto-commit)<a href="https://agentmods.dev/rules/quinnjr/google-mcp/auto-commit"><img src="https://agentmods.dev/badge/rules/quinnjr/google-mcp/auto-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/quinnjr/google-mcp/auto-commit"><img src="https://agentmods.dev/badge/rules/quinnjr/google-mcp/auto-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.00275 | $0.00275 |
| Opus 5.5 | $0.00110 | $0.00110 |
| Sonnet 5.5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
auto-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
Auto-Commit After Agent Tasks
After completing any task that modifies files in the repository, the agent should commit the changes.
Rules
-
Commit after every completed task - When a task is finished and files have been modified, stage and commit all changes before responding to the user.
-
Use conventional commits - Follow the git-flow commit message format:
<type>(<scope>): <subject> -
Push if remote is configured - After committing, push to the remote repository if one is set up.
-
Atomic commits - Each task should result in a single, focused commit that represents the complete change.
-
Don't commit partial work - Only commit when the task is fully complete and the code builds/lints successfully.
Workflow
After completing a task:
git add -A
git commit -m "<type>(<scope>): <descriptive message>"
git push # if remote exists
Exceptions
Do NOT commit when:
- The user explicitly asks not to commit
- The task is exploratory (reading files, searching code)
- The changes don't compile or have lint errors
- The user is still iterating on the 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.
- 1mo ago First seen · 43 lines · 275 tokens per session scan A 3ea2c2198604
auto-commit is a cursor rule published in the GitHub repository quinnjr/google-mcp (11 stars, last pushed 1mo ago), licensed MIT. It adds 275 tokens to every session, about $0.0011 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
conventional-commits
This rule defines the format for creating commit messages.
git-conventional-commit-messages
Cursor rules for Git development with conventional commit messages integration.
python-github-setup-cursorrules-prompt-file
Cursor rules for Python development with GitHub setup integration.
git
Git commit and branch rules that standardise how changes are described and organised. They also require explicit approval before committing code.
commit-message-generation-rule
Rules for writing consistent Git commit messages, using labels such as feat for a feature, fix for a bug, and docs for documentation. A commit message records one set of code changes.
commit-authorship
Git commits must be authored by the user only (no Cursor co-author).