project

A set of coding rules for a React, Vite, and TanStack project. It defines the approved tools, testing expectations, generated-file rules, and final checks.

In plain words
What is it for?
Use it when adding or changing features in this repository, especially when running tests, formatting, type checks, or builds.
Why use it?
It gives coding agents one source of truth for how this project should be changed and verified.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/whereissam/react-vite-tanstack-starter-template/project
Clone the repo
git clone --depth 1 https://github.com/whereissam/React-Vite-Tanstack-Starter-Template

Made for: Cursor.

Per session 150 This file is loaded in full into every session.
When invoked 150 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00150 $0.00150
Opus 5 $0.00075 $0.00075
Sonnet 5 $0.00030 $0.00030
Haiku 4.5 $0.00015 $0.00015

Measured 2d ago against content hash a2911a8a2d76, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

project 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.

.cursor/rules/project.mdc · 17 lines

What it actually says

Follow the conventions in AGENTS.md — it is the canonical instructions file for this repository.

Key points:

  • Use bun / bunx, never npm / npx.
  • Run bun run verify (lint + typecheck + format + test + build) before considering any change complete.
  • All new features require tests (Vitest + Testing Library, co-located).
  • src/routeTree.gen.ts is generated by TanStack Router — never edit by hand.
  • Only stage files related to the current task; never force push.
Changes

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.

  1. 2d ago First seen · 17 lines · 150 tokens per session scan A a2911a8a2d76

Subscribe to this mod's changes

project is a cursor rule published in the GitHub repository whereissam/React-Vite-Tanstack-Starter-Template (7 stars, last pushed 19d ago), licensed MIT. It adds 150 tokens to every session, about $0.0007 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-31.