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/innei-template/smart-webapp-templateWrote 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/innei-template/smart-webapp-template/routing)<a href="https://agentmods.dev/rules/innei-template/smart-webapp-template/routing"><img src="https://agentmods.dev/badge/rules/innei-template/smart-webapp-template/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/innei-template/smart-webapp-template/routing"><img src="https://agentmods.dev/badge/rules/innei-template/smart-webapp-template/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.00005 | $0.00476 |
| Opus 5.5 | $0.00002 | $0.00190 |
| Sonnet 5.5 | $0.00001 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
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
File-Based Routing System
This project uses vite-plugin-route-builder for file-based routing. Follow these patterns:
Route Types
Sync Routes: .sync.tsx files
- Synchronous routes without code splitting
- Used for critical pages that should load immediately
- Example:
src/pages/(main)/index.sync.tsxbecomes root route
Async Routes: .tsx files (without .sync)
- Asynchronous routes with lazy loading and code splitting
- Used for non-critical pages to optimize initial bundle size
- Example:
src/pages/about.tsxbecomes/aboutroute
Layout System
Layout Files: layout.tsx files serve as layout containers
- Use
<Outlet />within layout components to render child routes - Layouts automatically wrap their corresponding route segments
- Example:
src/pages/(main)/layout.tsxwraps all routes in the(main)group
Route Structure Examples
// Sync route - no code splitting
// File: src/pages/(main)/index.sync.tsx
export default function HomePage() {
return <div>Home Page</div>
}
// Async route - with code splitting
// File: src/pages/dashboard.tsx
export default function DashboardPage() {
return <div>Dashboard</div>
}
// Layout component
// File: src/pages/(main)/layout.tsx
import { Outlet } from 'react-router'
export default function MainLayout() {
return (
<div className="min-h-screen">
<nav>Navigation</nav>
<main>
<Outlet />
</main>
</div>
)
}
Generated Routes
- Routes are auto-generated in
src/generated-routes.ts - DO NOT EDIT the generated routes file manually
- The routing plugin handles all route generation automatically
Documentation Reference
For detailed usage, advanced patterns, and configuration options, always refer to the official documentation: https://github.com/Innei/vite-plugin-route-builder
Important: When encountering unclear routing patterns or advanced use cases, consult the official documentation before implementation.
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 · 69 lines · 5 tokens per session scan A 4c96ab32638e
routing is a cursor rule published in the GitHub repository innei-template/smart-webapp-template (143 stars, last pushed 12d ago), licensed MIT. It adds 5 tokens to every session and 476 once invoked, about $0.0000 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).