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/nedcodes-ok/cursorrules-collection/remixgit clone --depth 1 https://github.com/nedcodes-ok/cursorrules-collectionWhat 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.00395 | $0.00395 |
| Opus 5 | $0.00198 | $0.00198 |
| Sonnet 5 | $0.00079 | $0.00079 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
remix 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- remix — 100% identical, 0 lines differ
What it actually says
Remix Cursor Rules
You are an expert Remix developer. Follow these rules:
Data Flow
- Loaders for all data fetching — runs server-side before render
- Actions for all mutations — POST/PUT/DELETE through forms
- Never fetch in useEffect. If you need client data, use a resource route
- Return json() from loaders with proper HTTP status codes
- Throw Response objects for errors — Remix catches them in ErrorBoundary
Forms
- Use Remix for mutations, not fetch/axios
- Progressive enhancement: forms work without JS by default
- useNavigation() for pending UI, not custom loading state
- useFetcher for non-navigation mutations (like/bookmark buttons)
- Optimistic UI with useFetcher.formData
Routing
- File-based routes in app/routes/. Nested layouts via folder structure
- Pathless layout routes (_layout.tsx) for shared UI without URL segments
- Use loader data from parent routes via useRouteLoaderData
- Handle 404s with a $.tsx splat route
Error Handling
- ErrorBoundary in every route that loads data
- Throw new Response() with status codes, not Error objects
- isRouteErrorResponse() to distinguish expected vs unexpected errors
- Root ErrorBoundary as last resort — style it well
Sessions & Auth
- Cookie sessions via createCookieSessionStorage
- Redirect from loaders for auth guards — never render unauthorized content
- CSRF protection on all actions with custom tokens
Performance
- Return only needed data from loaders — no over-fetching
- headers() export for Cache-Control on static-ish routes
- Prefetch with for likely navigations
- Defer slow data with defer() and for streaming
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 · 47 lines · 395 tokens per session scan A 4796336dbfbb
remix is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (37 stars, last pushed 6mo ago), licensed MIT. It adds 395 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-30.