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/commerce-atoms/agents/00-agents-mdgit clone --depth 1 https://github.com/commerce-atoms/agentsWhat 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.00211 | $0.00211 |
| Opus 5 | $0.00105 | $0.00105 |
| Sonnet 5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
00-agents-md 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
ALWAYS read AGENTS.md at the repo root for the canonical rules. This .cursor/rules/ directory contains path-scoped overlays that complement AGENTS.md — they do not replace it.
If a rule appears here and not in AGENTS.md, treat it as a path-specific extension. If a rule contradicts AGENTS.md, treat AGENTS.md as authoritative and surface the contradiction so it can be resolved at the canonical source.
Per-tool overlay files (.cursor/rules/*.mdc, copilot-instructions.md, CLAUDE.md) are hand-maintained mirrors of the canonical sources in rules/core/*.md. Edit the canonical source first; the overlays are kept in sync by the maintainer. Generation from canonical sources is a planned future step (ADR 001).
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 · 11 lines · 211 tokens per session scan A 5cccab828323
00-agents-md is a cursor rule published in the GitHub repository commerce-atoms/agents (1 stars, last pushed 4mo ago), licensed MIT. It adds 211 tokens to every session, about $0.0011 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
read-xlsx
Reading, writing, diffing, and repairing spreadsheets (.xlsx) for AI agents via the xfa MCP server.
vue
Rules for Vue (2 and 3) single-file components.
frontend
UI/component conventions. Apply when building or changing user-facing frontend code.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.
cursorrules
Cursor rule "cursorrules" from googlarz/agents-sync, covering .cursorrules — managed by agents-sync v1.0.0, language: typescript / next.js 14 and run tests: npm test.
tailwind-css
Tailwind CSS: utility patterns, design tokens, component extraction.