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/jy315189/everything-cursor/auto-routinggit clone --depth 1 https://github.com/jy315189/everything-cursorWhat 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.00399 | $0.00399 |
| Opus 5 | $0.00199 | $0.00199 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
auto-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 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
Auto-Routing
When the user gives a task, silently classify it and apply the matching workflow:
| Signal in User Request | Task Type | Approach |
|---|---|---|
| "implement", "add", "create", "build" + feature description | New Feature | Plan → TDD → Review → Docs |
| "fix", "bug", "broken", "not working", "error" | Bug Fix | Reproduce with test → Fix → Verify |
| "build error", "compile error", "type error", TS error codes | Build Error | Diagnose → Fix → Verify build |
| "review", "check quality", "is this ok" | Code Review | Security → Correctness → Quality → Performance |
| "security", "vulnerability", "audit", "safe" | Security | OWASP scan → Remediate → Verify |
| "test", "write tests", "TDD", "coverage" | Testing | Interface → Failing test → Implement → Refactor |
| "e2e", "end to end", "playwright", "user flow" | E2E Testing | Map journey → Generate Playwright tests |
| "refactor", "clean up", "dead code", "unused" | Cleanup | Scan → Verify safety → Remove → Test |
| "architecture", "design", "which technology", "how should I structure" | Architecture | Multi-option analysis → Recommendation |
| "plan", "break down", "how to approach", "task list" | Planning | Requirements → Tasks → Dependencies → Risks |
| "docs", "documentation", "update readme", "changelog" | Docs | Detect changes → Update docs → Verify examples |
For multi-step tasks, announce the phases before starting. For simple tasks, just execute directly.
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 · 26 lines · 399 tokens per session scan A 56a4a08d42e4
auto-routing is a cursor rule published in the GitHub repository jy315189/everything-cursor (2 stars, last pushed 6mo ago), licensed MIT. It adds 399 tokens to every session, about $0.0020 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
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.