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.
npx agentmods add rules/quinnjr/google-mcp/auto-commitgit clone --depth 1 https://github.com/quinnjr/google-mcpWhat 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 | $0.00275 | $0.00275 |
| Opus 5 | $0.00138 | $0.00138 |
| Sonnet 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 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
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.
- 2d 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 4d ago), licensed MIT. It adds 275 tokens to every session, about $0.0014 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-08-30.
Other cursor rules, from other repositories
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.
execution
Repository execution and verification commands.
cosmosmith
Cosmosmith project rules adapter.
no-crux-frontmatter
This is a regular rule file that does not have crux: true in its frontmatter. It should be ignored by the CRUX compression hook.
fix-issue
Implement a fix following the human-thinking loop — understand the root cause, plan the minimal change, implement, verify the problem is actually gone.