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/KingEmma7/cursor-osWrote 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/kingemma7/cursor-os/no-auto-commit)<a href="https://agentmods.dev/rules/kingemma7/cursor-os/no-auto-commit"><img src="https://agentmods.dev/badge/rules/kingemma7/cursor-os/no-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/kingemma7/cursor-os/no-auto-commit"><img src="https://agentmods.dev/badge/rules/kingemma7/cursor-os/no-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.00128 | $0.00128 |
| Opus 5.5 | $0.00051 | $0.00051 |
| Sonnet 5.5 | $0.00026 | $0.00026 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
no-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
No auto-commit
Never run git commit, git push, git tag, or npm publish unless the user explicitly asks (e.g. "commit this", "push", "publish").
- Show the user what changed and let them decide.
- Use
git difforgit statusoutput to summarise changes in your response instead. - If you are about to perform a git write operation, stop and confirm first.
This applies regardless of how small, clean, or obviously-correct the change appears.
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 · 15 lines · 128 tokens per session scan A 9e2b4f90afd3
no-auto-commit is a cursor rule published in the GitHub repository KingEmma7/cursor-os (2 stars, last pushed 20d ago), licensed MIT. It adds 128 tokens to every session, about $0.0005 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-31.
Other cursor rules, from other repositories
04-commit-style
Branch, commit, and PR conventions.
git-workflow
Git workflow: commits, branches, PRs, history management.
git
A set of rules for using Git, a tool for tracking code changes. It covers commits, branches, and general version-control principles.
git-commit-confirmation
Always ask user to confirm before creating git commits.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.
conventional-commits
Conventional Commits format enforced by pre-commit hooks.