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/commerce-atoms/agentsWrote 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/commerce-atoms/agents/20-routing)<a href="https://agentmods.dev/rules/commerce-atoms/agents/20-routing"><img src="https://agentmods.dev/badge/rules/commerce-atoms/agents/20-routing/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/commerce-atoms/agents/20-routing"><img src="https://agentmods.dev/badge/rules/commerce-atoms/agents/20-routing.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.00205 | $0.00205 |
| Opus 5.5 | $0.00082 | $0.00082 |
| Sonnet 5.5 | $0.00041 | $0.00041 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
20-routing 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 1mo 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
This is a Cursor-specific overlay. Canonical source: rules/core/routing.md.
Single source of truth
app/routes.tsis the only routing manifest.- Do not add additional route manifest files.
- Do not add a second routing entrypoint that duplicates routing definitions.
No filesystem routing
- Do not rely on
app/routes/*filesystem discovery as the routing source of truth.
Explicit mapping
- Each URL pattern maps explicitly to a route module file under
app/modules/*. - Avoid abstractions that generate, auto-compose, or implicitly register routes.
Layout nesting
- UI routes are nested under the layout shell route (owned by
app/layout/*). - Resource routes (
robots.txt,sitemap.xml, etc.) remain outside layout nesting.
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.
- 1mo ago First seen · 29 lines · 205 tokens per session scan A 35e09e0347c9
20-routing is a cursor rule published in the GitHub repository commerce-atoms/agents (1 stars, last pushed 1mo ago), licensed MIT. It adds 205 tokens to every session, about $0.0008 per session on Opus 5.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
stripe
Stripe payment integration, webhooks, checkout, and subscriptions.
bootstrap-alwayson
Minimal always-required LLM fixes.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
read-xlsx
Reading, writing, diffing, and repairing spreadsheets (.xlsx) for AI agents via the xfa MCP server.
RULE
Network troubleshooting — systematic diagnosis and resolution for connectivity, DNS, proxy, SSL, HTTP errors.
vue
Rules for Vue (2 and 3) single-file components.