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/sitecore/xmcloud-starter-js/safetygit clone --depth 1 https://github.com/Sitecore/xmcloud-starter-jsWhat 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.00522 | $0.00522 |
| Opus 5 | $0.00261 | $0.00261 |
| Sonnet 5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
safety 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
Safety Rules
Do Not Edit Compiled Artifacts
Never edit compiled or generated files:
- Node modules:
node_modules/contains installed packages - Build outputs:
.next/,dist/,out/,build/are generated during build - Cache directories:
.cache/,.sitecore/(except component-map.ts) - Lock files:
package-lock.json,yarn.lock,pnpm-lock.yaml - Source maps:
*.js.map,*.css.map,*.d.ts.map
Do Not Edit Configuration Files
Avoid modifying sensitive configuration:
- Sitecore configs:
scjssconfig.json,.sitecore/user.json - Docker files:
Dockerfile,docker-compose*.yml - CI/CD configs:
.github/workflows/, deployment configurations
Do Not Edit Package Files
Never modify package artifacts:
- Sitecore packages:
*.itempackage,*.sicpackage - Archive files:
*.tgz,*.tar.gz,*.zip - Binary files:
*.exe,*.dll,*.obj
Do Not Edit Environment Files
Never commit or edit sensitive environment files:
- Local environment:
.env.local,.env.*.local - Secret files:
*.deploysecret.config - User-specific configs:
.sitecore/user.json
Source Files Only
Focus editing on:
- Source code:
.ts,.tsx,.js,.jsxfiles insrc/ - Configuration:
next.config.js,tsconfig.json,package.json - Documentation:
README.md,CONTRIBUTING.md - Styles:
.css,.scssfiles - Component maps:
.sitecore/component-map.ts
When in Doubt
If unsure whether to edit a file:
- Check if it's in
node_modules/- never edit - Check if it's generated during build - never edit
- Check if it contains secrets - never edit
- Ask yourself: "Did I create this file?" - if no, be cautious
Referenced: @.gitignore @.cursorignore @examples/*/package.json
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 · 59 lines · 522 tokens per session scan A c17d991770e3
safety is a cursor rule published in the GitHub repository Sitecore/xmcloud-starter-js (29 stars, last pushed 8d ago), licensed Apache-2.0. It adds 522 tokens to every session, about $0.0026 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
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.