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/elliothux/trunktailWrote 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/elliothux/trunktail/tanstack-react-router_routing)<a href="https://agentmods.dev/rules/elliothux/trunktail/tanstack-react-router_routing"><img src="https://agentmods.dev/badge/rules/elliothux/trunktail/tanstack-react-router_routing/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/elliothux/trunktail/tanstack-react-router_routing"><img src="https://agentmods.dev/badge/rules/elliothux/trunktail/tanstack-react-router_routing.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.16868 | $0.16868 |
| Opus 5.5 | $0.06747 | $0.06747 |
| Sonnet 5.5 | $0.03374 | $0.03374 |
| Haiku 4.5 | $0.01687 | $0.01687 |
Grade A, and why
tanstack-react-router_routing 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 1,956 lines · 16,868 tokens per session scan A 394880f1a1b4
tanstack-react-router_routing is a cursor rule published in the GitHub repository elliothux/trunktail (21 stars, last pushed 8mo ago), with no licence file. It adds 16,868 tokens to every session, about $0.0675 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
rules.general
A project rule set for a Next.js application using TypeScript, React, Tailwind CSS, shadcn/ui, Radix UI, and Lucide icons.
cursorrules
Use the latest version of Shadcn to install new components, like this command to add a button component.
frontend-react
Complete React component patterns, hooks, and state management with shadcn/ui for POS System.
cursorrules
Use the latest version of Shadcn to install new components, like this command to add a button component.
notes
The .cursor/notes folder contains notes about this project. The notes form a knowledge base about the project to be used by the AI Agents working on the project. They should help you when working with the same code again in the future.
changelog-conventions
Always update the Changelog.md in the corresponding sub project upon changing the project code!