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/charlee-x/effect-cursor-rules/react-router-v7-patternsgit clone --depth 1 https://github.com/CharLEE-X/effect-cursor-rulesWhat 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.00000 | $0.03047 |
| Opus 5 | $0.00000 | $0.01523 |
| Sonnet 5 | $0.00000 | $0.00609 |
| Haiku 4.5 | $0.00000 | $0.00305 |
Grade A, and why
react-router-v7-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Router v7 (Remix) Best Practices
Overview
React Router v7 is the evolution of Remix, providing server-side rendering, data loading, and modern routing patterns. Follow these patterns for optimal performance and user experience.
Route Structure and Organization
✅ CORRECT Route Organization
// apps/frontend/src/routes/
├── _layout.tsx // Root layout
├── _auth.tsx // Auth layout
├── page/
│ ├── index/ // Home page
│ │ ├── route.tsx // Main route file
│ │ ├── featured-blogs.tsx // Page components
│ │ └── hero.tsx
│ └── about/
│ └── route.tsx
├── api/
│ ├── auth/
│ │ └── login.tsx // API routes
│ └── blog/
│ └── featured.tsx
└── ui/
├── blog/
│ └── route.tsx // UI routes
└── profile/
└── route.tsx
❌ WRONG Route Organization
// Don't mix concerns in single files
├── routes/
│ ├── everything-in-one-file.tsx // Too much in one file
│ ├── random-structure/ // Inconsistent naming
│ └── no-clear-separation/ // Mixed API and UI routes
Data Loading Patterns
✅ CORRECT Loader Implementation
// route.tsx
import { LoaderFunctionArgs } from 'react-router'
import { BlogPostService } from '~/.server/services/BlogPostService'
import { E } from '~/lib/effect'
export const loader = async ({ request }: LoaderFunctionArgs) => {
const url = new URL(request.url)
const page = Number(url.searchParams.get('page')) || 1
// Use Effect-TS for data loading
const featuredBlogPostsPromise = E.runPromise(
BlogPostService.getFeaturedBlogPosts({ page, limit: 6 }).pipe(
E.provide(BlogPostService.Default)
)
)
return {
featuredBlogPostsPromise,
meta: {
title: 'T6C - Motorcycle Community',
description: 'Join the ultimate motorcycle building community'
}
}
}
// Component using the data
export default function HomePage() {
const { featuredBlogPostsPromise } = useLoaderData<typeof loader>()
return (
<div>
<Suspense fallback={<LoadingSkeleton />}>
<Await
resolve={featuredBlogPostsPromise}
errorElement={<ErrorComponent />}
>
{(data) => <FeaturedBlogs data={data} />}
</Await>
</Suspense>
</div>
)
}
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 · 478 lines · 3,047 tokens per session scan A e72ba7e0d1d9
react-router-v7-patterns is a cursor rule published in the GitHub repository CharLEE-X/effect-cursor-rules (6 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,047 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-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.