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/chand1012/cursorrulesWrote 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/chand1012/cursorrules/react-router-data)<a href="https://agentmods.dev/rules/chand1012/cursorrules/react-router-data"><img src="https://agentmods.dev/badge/rules/chand1012/cursorrules/react-router-data/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/chand1012/cursorrules/react-router-data"><img src="https://agentmods.dev/badge/rules/chand1012/cursorrules/react-router-data.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.00000 | $0.00484 |
| Opus 5.5 | $0.00000 | $0.00194 |
| Sonnet 5.5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
react-router-data 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Router Data Mode Best Practices
Route Configuration
- Use
createBrowserRouterfor Data Mode setup - Define loaders and actions at the route level
- Implement nested routes for layout organization
- Use lazy loading for routes and components
- Include error boundaries in route definitions
- Specify
shouldRevalidateto control data fetching
Loaders
- Decouple data fetching from components
- Ensure type safety with TypeScript or Zod
- Handle loading states with
SuspenseandOutlet - Use
useLoaderDatafor accessing loader data - Implement authentication checks in loaders
- Optimize with lazy-loaded loaders
Actions
- Use
<Form>for declarative form submissions - Leverage
useSubmitfor programmatic submissions - Utilize
useFetcherfor non-navigating actions - Differentiate between client and server actions
- Implement redirects after successful actions
- Prefer uncontrolled forms for simplicity
Components
- Use route props for type-safe data access
- Implement error boundaries for robust error handling
- Create reusable components for forms and UI
- Use
<Outlet>for rendering nested routes - Keep components focused on single responsibilities
- Avoid manual data fetching in components
Navigation
- Use
<Link>for declarative navigation - Implement
useNavigatefor programmatic navigation - Handle navigation states with
useNavigation - Ensure loaders are triggered on navigation
- Provide feedback during navigation transitions
- Avoid direct URL manipulation
Performance
- Lazy-load routes, loaders, and components
- Control revalidation with
shouldRevalidate - Use
Suspensefor efficient loading states - Optimize loader data fetching with caching
- Avoid unnecessary loader calls
- Profile navigation performance
Error Handling
- Define error boundaries in routes
- Use
useRouteErrorfor error access - Display user-friendly error messages
- Implement fallback UI for errors
- Handle loader and action errors gracefully
- Log errors for debugging
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 · 71 lines · 484 tokens per session scan A f17d9965d622
react-router-data is a cursor rule published in the GitHub repository chand1012/cursorrules (14 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 484 tokens. 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
windsurfrules
Create detailed components with these requirements.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
new-component
Workflow for creating new React components.
tanstack-react-router_routing
TanStack Router: Routing.