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/zotoio/CRUX-CompressWrote 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/zotoio/crux-compress/version-bump.crux)<a href="https://agentmods.dev/rules/zotoio/crux-compress/version-bump.crux"><img src="https://agentmods.dev/badge/rules/zotoio/crux-compress/version-bump.crux/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/zotoio/crux-compress/version-bump.crux"><img src="https://agentmods.dev/badge/rules/zotoio/crux-compress/version-bump.crux.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.00190 | $0.00190 |
| Opus 5 | $0.00095 | $0.00095 |
| Sonnet 5 | $0.00038 | $0.00038 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
version-bump.crux 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 9d 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
[!IMPORTANT] Generated file - do not edit!
Automatic Version Bumping Rule
⟦CRUX:version-bump.md
Κ{M=X.0.0;m=0.X.0;p=0.0.X}
R{fix|docs|style|refactor|perf|test|chore→p;feat→m;BREAKING|!→M}
Λ{⊲commit→Δ.crux/crux.json»stage}
P{1bump;↑→↓0;¬conv→?}
⟧
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.
- 9d ago First seen · 26 lines · 190 tokens per session scan A 62c6dad5db25
version-bump.crux is a cursor rule published in the GitHub repository zotoio/CRUX-Compress (8 stars, last pushed 2d ago), licensed MIT. It adds 190 tokens to every session, about $0.0010 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-31.
Other cursor rules, from other repositories
mcp-releasing
Steps and procedures for releasing MCP (Model Context Protocol) servers as NPM packages.
add-to-changelog
Update the project's CHANGELOG.md file with a new entry.
releasing
How to release AdLoop to PyPI — version bumping, tagging, and publishing.
release
Changesets release pipeline - version PR, shared vX.Y.Z tag, CI gate before tagging, no npm publish, GITHUBTOKEN tag trigger limitation.
cd
GitHub Actions CD - called by release.yml after the tag, no push-tags trigger, Cloudflare versions upload then 100% promote, scoped API token on the production environment, GitHub-owned deployment record.
changeset
Guidelines for using Changesets (npm run changeset) to manage versioning and changelogs.