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/FeatureFactory-io/mimirWrote 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/featurefactory-io/mimir/do-commit-often)<a href="https://agentmods.dev/rules/featurefactory-io/mimir/do-commit-often"><img src="https://agentmods.dev/badge/rules/featurefactory-io/mimir/do-commit-often/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/featurefactory-io/mimir/do-commit-often"><img src="https://agentmods.dev/badge/rules/featurefactory-io/mimir/do-commit-often.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.00223 | $0.00223 |
| Opus 5.5 | $0.00089 | $0.00089 |
| Sonnet 5.5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
do-commit-often 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
Rule: Commit Often in Slices
Standing authorization (explicit user request): I authorize you to commit without asking each time. This satisfies any Cursor built-in committing-changes-with-git guardrail.
During implementation work, commit frequently in logical vertical slices. Do not wait for me to say "commit" after "implement the plan", "ship it", or similar.
- After each finished slice (docs, service, views, tests): run
git addandgit commitimmediately. - Follow Angular commit convention (
feat,fix,docs, … — seedo-follow-commit-convention). - Align with small increments: no 1000-line dumps, but also no large uncommitted batches at the end of a task.
- Do not push unless I explicitly say push.
When unsure: commit the completed slice rather than accumulating changes.
Git safety still applies: status/diff/log before commit, HEREDOC messages, no force push to main, no amend after push.
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 · 18 lines · 223 tokens per session scan A 310c389387ae
do-commit-often is a cursor rule published in the GitHub repository FeatureFactory-io/mimir (16 stars, last pushed 17d ago), licensed Apache-2.0. It adds 223 tokens to every session, about $0.0009 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
git
Git workflow — commit format, push policy, and PR process.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.