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/arango-solutions/arango-sparql-pyWrote 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/arango-solutions/arango-sparql-py/checkpoint-regularly)<a href="https://agentmods.dev/rules/arango-solutions/arango-sparql-py/checkpoint-regularly"><img src="https://agentmods.dev/badge/rules/arango-solutions/arango-sparql-py/checkpoint-regularly/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/arango-solutions/arango-sparql-py/checkpoint-regularly"><img src="https://agentmods.dev/badge/rules/arango-solutions/arango-sparql-py/checkpoint-regularly.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.00272 | $0.00272 |
| Opus 5.5 | $0.00109 | $0.00109 |
| Sonnet 5.5 | $0.00054 | $0.00054 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
checkpoint-regularly 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
Checkpoint Regularly
"Commit early, push often, never lose work."
Large, uncommitted changesets are disasters waiting to happen.
Checkpoint Triggers
You MUST commit and push when:
| Trigger | Why |
|---|---|
| Feature complete | Logical unit of work done |
| Tests passing | Known-good state worth preserving |
| Before risky refactor | Safety net if refactor fails |
| After ~30 minutes of work | Time-based protection |
| Before switching tasks | Clean handoff point |
| Before ending session | Never leave work uncommitted |
Git Discipline
Commit Messages
# GOOD: Descriptive, scoped
git commit -m "feat(wormhole): wire initializeCentroids to respect config"
git commit -m "fix(aboyeur): integrate createWorkItemsFromChecklist"
# BAD: Vague
git commit -m "updates"
git commit -m "wip"
Rules
- One logical change per commit
- If you can't describe it in one line, it's too big
- Push immediately after every commit — push is free, losing work is expensive
Checkpoint. Push. Repeat.
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 · 45 lines · 272 tokens per session scan A 893fe6e76f50
checkpoint-regularly is a cursor rule published in the GitHub repository arango-solutions/arango-sparql-py (2 stars, last pushed 10d ago), licensed MIT. It adds 272 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-09-07.
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.