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/virastack/aiWrote 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/virastack/ai/tanstack-start)<a href="https://agentmods.dev/rules/virastack/ai/tanstack-start"><img src="https://agentmods.dev/badge/rules/virastack/ai/tanstack-start/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/virastack/ai/tanstack-start"><img src="https://agentmods.dev/badge/rules/virastack/ai/tanstack-start.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.00000 | $0.01057 |
| Opus 5.5 | $0.00000 | $0.00423 |
| Sonnet 5.5 | $0.00000 | $0.00211 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
tanstack-start 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-start — 95% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TanStack Start Constitution
Constraints
- Route Definition: Always use
createFileRoute. Path MUST strictly match the file system location. - Component Scope: Keep route files thin. Only orchestrate routing and data. Move UI and business logic to
src/features. - Nested Layouts: Use the
<Outlet />component in parent routes to render child routes. If a route has children, the parent component MUST render<Outlet />. - Data Loading: Fetch all route-level data in
loader. Consume viaRoute.useLoaderDataoruseSuspenseQuery. - Guards: Put auth, redirects, and preconditions in
beforeLoad. - Hydration: Rely on loader prefetching for data hydration. Do not use Next.js-specific patterns like manual dehydration.
- Server Functions: Wrap all backend-only logic in standalone
serverFn. Functions MUST act as a bridge to the API layer; keep database orchestration and business logic inside src/features/api or helpers. - Search Params: Validate all search params with
validateSearchusing a Zod schema. Never trust raw search values. - i18n Implementation: Use
paraglide-jsfor translations. Follow the patterns defined ini18n.mdc. - Error Handling: Provide
errorComponentfor failure states. Handle expected errors in the loader. - Loading UI: Provide
pendingComponentfor async states when needed. - Not Found: Provide
notFoundComponentfor missing resources. - Head/SEO: Define metadata with the
headproperty. Keep it deterministic and typed. - Sync: Ensure route paths are kept in sync via
tsr watchcommand. - Guard Security: Enforce session and permission checks within
beforeLoador dedicated middleware beforeserverFnexecution.
Bans
- Client-Side Fetching: Fetching data inside the component body via
useEffectoruseQuery(without loader prefetch) is FORBIDDEN. - Inline serverFn: Defining
serverFninside a component or route definition is FORBIDDEN. They MUST be exported as standalone constants. - Next.js Conventions: Using
"use server"directives,page.tsxnaming, or Next.js-specific hooks (useRouterfrom next/navigation) is STRICTLY FORBIDDEN. - Untyped Routes: Navigating via string paths without type-safety (using
LinkorMapswithout thetoproperty pointing to a valid route) is FORBIDDEN. - Insecure Env Vars: Forbidden to store secrets or private keys in environment variables with
VITE_prefixes.
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 · 105 lines · 0 tokens per session scan A 54bdedbcb46a
tanstack-start is a cursor rule published in the GitHub repository virastack/ai (23 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,057 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-30.
Other cursor rules, from other repositories
sync-api-endpoints
When HTTP routes change, update the web UI API page and API docs together.
marker-triage
Triage a Marker.io website-feedback backlog at scale. Use when asked to go through, categorize, prioritize, deduplicate, or make sense of many Marker.io issues at once. Splits content fixes from functional bugs, groups by page, rates criticality, flags duplicates and repeat reporters, surfaces quick wins, lists…
marker-insights
Aggregate Marker.io website feedback into recurring patterns. Use when asked to find the most common issues on a site, which pages get the most feedback, recurring content problems, or the content-vs-bug split across many Marker.io reports, and produce a prioritized brief for a website team or agency. Read-only: it…
developer
Senior Developer persona — implements backend user stories, production code, git workflow. Use when coding backend features, writing tests, or implementing API endpoints.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.