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/ranyitz/aicm/opt-in-rulegit clone --depth 1 https://github.com/ranyitz/aicmWrote 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/ranyitz/aicm/opt-in-rule)<a href="https://agentmods.dev/rules/ranyitz/aicm/opt-in-rule"><img src="https://agentmods.dev/badge/rules/ranyitz/aicm/opt-in-rule.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.00004 | $0.00039 |
| Opus 5 | $0.00002 | $0.00019 |
| Sonnet 5 | $0.00001 | $0.00008 |
| Haiku 4.5 | $0.00000 | $0.00004 |
Grade A, and why
opt-in-rule 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
- Follow semantic versioning for releases
- Use conventional commits for commit messages
- Run tests before pushing changes
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 · 8 lines · 4 tokens per session scan A 6d2c5459a121
opt-in-rule is a cursor rule published in the GitHub repository ranyitz/aicm (36 stars, last pushed 5mo ago), licensed MIT. It adds 4 tokens to every session and 39 once invoked, about $0.0000 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-30.
Other cursor rules, from other repositories
commit-flow
Cursor rule "commit-flow" from xuliang2024/cutcli-cookbook, covering 提交流程, 提交前自检（必跑）, conventional commits, pr 流程 and ci 必过线.
mojiemoji-github
Decorate Japanese GitHub Markdown with mojiemoji before posting.
git-authoring
Conventional Commit, pull-request, release-note, and PR-review conventions for this repository.
release-commit-analysis-auto
This rule analyzes commits to determine if they should trigger a version bump. It categorizes conventional and non-conventional commits into Features, Bug Fixes, Breaking Changes, Documentation, and Other. It uses intelligent keyword matching for non-conventional commits and analyzes file changes to help categorize…
git-workflow
Cloud Agents MUST run git add, git commit, and git push before ending their response when they have made code changes. Do not end your turn without pushing. ALWAYS use Pull Requests instead of pushing directly to main.
git-workflow
Git branching and PR workflow.