Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/openstory-so/openstorynpx agentmods add rules/openstory-so/openstory/tanstack-react-router_apiWrote 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/openstory-so/openstory/tanstack-react-router_api)<a href="https://agentmods.dev/rules/openstory-so/openstory/tanstack-react-router_api"><img src="https://agentmods.dev/badge/rules/openstory-so/openstory/tanstack-react-router_api/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/openstory-so/openstory/tanstack-react-router_api"><img src="https://agentmods.dev/badge/rules/openstory-so/openstory/tanstack-react-router_api.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.32828 | $0.32828 |
| Opus 5.5 | $0.13131 | $0.13131 |
| Sonnet 5.5 | $0.06566 | $0.06566 |
| Haiku 4.5 | $0.03283 | $0.03283 |
Grade A, and why
tanstack-react-router_api 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- tanstack-react-router_api — 100% identical, 317 lines differ
How it starts
The opening of the file, as written. The whole thing — 4,390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ActiveLinkOptions type
The ActiveLinkOptions type extends the LinkOptions type and contains additional options that can be used to describe how a link should be styled when it is active.
type ActiveLinkOptions = LinkOptions & {
activeProps?:
| React.AnchorHTMLAttributes<HTMLAnchorElement>
| (() => React.AnchorHTMLAttributes<HTMLAnchorElement>)
inactiveProps?:
| React.AnchorHTMLAttributes<HTMLAnchorElement>
| (() => React.AnchorHTMLAttributes<HTMLAnchorElement>)
}
ActiveLinkOptions properties
The ActiveLinkOptions object accepts/contains the following properties:
activeProps
React.AnchorHTMLAttributes<HTMLAnchorElement>- Optional
- The props that will be applied to the anchor element when the link is active
inactiveProps
- Type:
React.AnchorHTMLAttributes<HTMLAnchorElement> - Optional
- The props that will be applied to the anchor element when the link is inactive
AsyncRouteComponent type
The AsyncRouteComponent type is used to describe a code-split route component that can be preloaded using a component.preload() method.
type AsyncRouteComponent<TProps> = SyncRouteComponent<TProps> & {
preload?: () => Promise<void>
}
FileRoute class
[!CAUTION] This class has been deprecated and will be removed in the next major version of TanStack Router. Please use the
createFileRoutefunction instead.
The FileRoute class is a factory that can be used to create a file-based route instance. This route instance can then be used to automatically generate a route tree with the tsr generate and tsr watch commands.
FileRoute constructor
The FileRoute constructor accepts a single argument: the path of the file that the route will be generated for.
Constructor options
- Type:
stringliteral - Required, but automatically inserted and updated by the
tsr generateandtsr watchcommands. - The full path of the file that the route will be generated from.
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 · 4,390 lines · 32,828 tokens per session scan A 155a3a08daaf
tanstack-react-router_api is a cursor rule published in the GitHub repository openstory-so/openstory (676 stars, last pushed yesterday), licensed MIT. It adds 32,828 tokens to every session, about $0.1313 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 cursor rules, from other repositories
windsurfrules
Create detailed components with these requirements.
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.
project-structure
Folder layout for Next.js App Router and Vite + React variants.
rendering-and-memoization
React anti-patterns R9, R11, R12 — index-as-key in dynamic lists, context overuse for frequent updates, inline functions breaking memoization. Load on a review hit for any of these codes, or when tuning render performance.
react-basics-state
A set of React rules for managing shared application state with Context API and useReducer. React is a JavaScript library for building user interfaces; shared state is information used by multiple parts of an interface.