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/featurefactory-io/mimir/do-check-previous-commitsgit 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-check-previous-commits)<a href="https://agentmods.dev/rules/featurefactory-io/mimir/do-check-previous-commits"><img src="https://agentmods.dev/badge/rules/featurefactory-io/mimir/do-check-previous-commits.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00060 |
| Opus 5 | $0.00000 | $0.00030 |
| Sonnet 5 | $0.00000 | $0.00012 |
| Haiku 4.5 | $0.00000 | $0.00006 |
Grade A, and why
do-check-previous-commits 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 4d 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: Check Previous Commits
When you encounter missing imports, parts of the files missing, or files missing - always check:
- Previous commit.
- Commit from which branch originates.
Likely you will find it there and can restore from there.
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.
- 4d ago First seen · 12 lines · 0 tokens per session scan A d1a54114c511
do-check-previous-commits is a cursor rule published in the GitHub repository FeatureFactory-io/mimir (13 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 60 tokens. 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
Conventional commit message format for git commits.
git-conventions
See CONTRIBUTING.md → "PR & commit conventions" for PR title format, commit messages, and branch naming.
git
辅助生成 Git 提交信息和执行 Git 命令.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
commit-and-push
Commit (conventional commit) files and push to the remote repository.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.