Borrowing it
Nothing to install: this file belongs to iloveitaly/llm-ide-rules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/iloveitaly/llm-ide-rules/master/.github/instructions/react-router.instructions.mdgit clone --depth 1 https://github.com/iloveitaly/llm-ide-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/instructions/iloveitaly/llm-ide-rules/react-router)<a href="https://agentmods.dev/instructions/iloveitaly/llm-ide-rules/react-router"><img src="https://agentmods.dev/badge/instructions/iloveitaly/llm-ide-rules/react-router/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/instructions/iloveitaly/llm-ide-rules/react-router"><img src="https://agentmods.dev/badge/instructions/iloveitaly/llm-ide-rules/react-router.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.01035 | $0.01035 |
| Opus 5.5 | $0.00414 | $0.00414 |
| Sonnet 5.5 | $0.00207 | $0.00207 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
llm-ide-rules react-router.instructions.md 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 28d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Router
- You are using the latest version of React Router (v7).
- Always include the suffix
Pagewhen naming the default export of a route. - The primary export in a routes file should specify
loaderDatalikeexport default function RouteNamePage({ loaderData }: Route.ComponentProps).loaderDatais the return value fromclientLoader. - Use
href("/products/:id", { id: "abc123" })to generate a url path for a route managed by the application.- Look at routes.ts to determine what routes and path parameters exist.
- Use
export async function clientLoader(loaderArgs: Route.ClientLoaderArgs)to define aclientLoaderon a route. - Do not define
Route.*types, these are autogenerated and can be imported fromimport type { Route } from "./+types/routeFileName" - If URL parameters or query string values need to be checked before rendering the page, do this in a
clientLoaderand not in auseEffect - Never worry about generating types using
pnpm - Use
<AllMeta />instead of MetaFunction or individual<meta />tags - Move derived config and business rules to the backend (computed fields, calculations, etc). Do not grow client-only sources of truth.
- Use outlets to store global config (such as Stripe keys, application settings, etc).
- Hide repeated mobile/desktop conditional styling behind a helper; individual components should not re-encode breakpoints
- Use the following pattern to reference query string values (i.e.
?theQueryStringParam=value)
const [searchParams, _setSearchParams] = useSearchParams()
// searchParams contains the value of all query string parameters
const queryStringValue = searchParams.get("theQueryStringParam")
Loading Mock Data
Don't load mock data in the component function with useEffect. Instead, load data in a clientLoader:
// in mock.ts
export async function getServerData(options: any) {
// ...
}
// in web/app/routes/**/*.ts
export async function clientLoader(loaderArgs: Route.ClientLoaderArgs) {
// no error reporting is needed, this will be handled by the `getServerData`
// mock loading functions should return result in a `data` key
const { data } = await getServerData({
/* ... */
});
// the return result here is available in `loaderData`
return data;
}
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.
- 28d ago Changed · -1 lines 868200d067e6
- 1mo ago Changed · +3 lines · +67 tokens per session 560d9cecd9a3
- 1mo ago First seen · 93 lines · 968 tokens per session scan A 2ab225d40943
llm-ide-rules react-router.instructions.md is an instructions file published in the GitHub repository iloveitaly/llm-ide-rules (13 stars, last pushed yesterday), licensed MIT. It adds 1,035 tokens to every session, about $0.0041 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.