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/rules-best-practicesgit clone --depth 1 https://github.com/ranyitz/aicmWhat 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.00264 |
| Opus 5 | $0.00000 | $0.00132 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
rules-best-practices 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 2d 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 Structure
---
description: Clear, one-line description
globs: # Empty for alwaysApply: true, glob pattern for alwaysApply: false
alwaysApply: boolean
---
## Main Points as headers
- Sub-points with specifics
Frontmatter Guidelines
alwaysApply: truerequires emptyglobskey- Use
alwaysApply: truewithglobs:(no value) for rules that apply to entire codebase - Use
alwaysApply: falsewithglobs: **/*.tsfor rules targeting specific file types/paths
- Use
File References
- Rules or Code: @rules/filename.mdc
Code Examples
// ✅ DO: Good pattern
const correct = true;
// ❌ DON'T: Anti-pattern
const incorrect = false;
Guidelines
- Start with overview, then specifics
- Write concisely - include only what's necessary
- Use bullet points
- Include both DO/DON'T examples
- Reference existing code
- Do not repeat yourself by cross-referencing other rule file
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.
- 2d ago First seen · 47 lines · 0 tokens per session scan A 67aa2cd56967
rules-best-practices is a cursor rule published in the GitHub repository ranyitz/aicm (36 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 264 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.