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/goranerhartic/cursor-development-rules/routinggit clone --depth 1 https://github.com/GoranErhartic/cursor-development-rulesWrote 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/goranerhartic/cursor-development-rules/routing)<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/routing"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/routing.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.00713 |
| Opus 5 | $0.00008 | $0.00357 |
| Sonnet 5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Routing with React Router v7
Setup
createBrowserRouter([...])+RouterProvider router={router}; per-routeelement,errorElement,loader,action- Children:
index: truefor index route;path: 'segment'for nested routes; layout wraps with<Outlet />
Loaders
- Signature:
async function loader({ params, request }: LoaderFunctionArgs): Promise<Data> - Params: Validate
params.id; thrownew Response('message', { status: 404 })orredirect('/path')on auth failure - Search params:
new URL(request.url).searchParams.get('q') - Usage:
useLoaderData<Data>()in component
Actions
- Signature:
async function action({ params, request }: ActionFunctionArgs) - Form data:
await request.formData();formData.get('name') - Return
redirect('/path')on success; return{ errors }for validation; throw or return error for 4xx/5xx - Usage:
<Form method="post">;useActionData<typeof action>();useNavigation().state === 'submitting'for loading
Navigation
- Declarative:
<Link to="/path">,<NavLink to="..." className={({ isActive }) => ...}>;<Link to=".." relative="path">;replace - Programmatic:
useNavigate()—navigate(path),navigate(-1),navigate(path, { replace: true, state }) - Search params:
useSearchParams(); update withsetSearchParams(prev => new URLSearchParams(...))
Route Guards
- Loader-based: In loader, check auth; if unauthenticated
throw redirect('/login?redirectTo=' + pathname); if forbidden thrownew Response(..., { status: 403 }) - Component-based:
<RequireAuth><Outlet /></RequireAuth>— inside, check auth and render<Navigate to="/login" state={{ from: location }} replace />if not authenticated
Key Hooks
useLoaderData<T>(),useActionData<T>(),useNavigation()(state: idle|submitting|loading),useFetcher()(background submit without navigation),useSearchParams(),useLocation(),useParams()
Error Handling
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.
- yesterday First seen · 54 lines · 15 tokens per session scan A 99b534403642
routing is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 713 once invoked, about $0.0001 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-09-03.
Other cursor rules, from other repositories
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
mobx
Definitive guidelines for structuring MobX applications with React, focusing on predictable state management, optimal rendering, and modern best practices.
backend
Backend development rules for TT Studio - AI model management backend.
new-component
Workflow for creating new React components.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.