cursorrules

A short Cursor rules file that points developers to AGENTS.md as the project’s main instruction file. It records conventions for npm, routes, server code, React components, types, and environment variables.

In plain words
What is it for?
Guiding work in a React application that uses TanStack Router, Hono, server-side rendering, and npm. It specifies where routes and server APIs belong and how environment variables are read.
Why use it?
It gives coding agents a concise set of project constraints while keeping the full instructions in one source file. This helps prevent edits to generated files and keeps new code consistent.

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/bskimball/tanstack-hono/cursorrules
Clone the repo
git clone --depth 1 https://github.com/bskimball/tanstack-hono

Made for: Cursor.

Per session 177 This file is loaded in full into every session.
When invoked 177 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.00177 $0.00177
Opus 5 $0.00088 $0.00088
Sonnet 5 $0.00035 $0.00035
Haiku 4.5 $0.00018 $0.00018

Measured yesterday against content hash 984ca1ba3706, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursorrules 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 yesterday.

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.

.cursorrules · 27 lines

What it actually says

Cursor Rules

This file is intentionally short. Use AGENTS.md as the source of truth.

Non-Negotiables

  • Package manager: npm
  • Do not edit src/routeTree.gen.ts (auto-generated)
  • Routes: src/routes/ using TanStack Router createFileRoute
  • Server/API: add Hono routes in src/entry-server.tsx

Conventions (Prefer)

  • React components: use function declarations for named components
  • Types: prefer interface for object shapes when reasonable
  • Imports: @/ alias or relative imports are both ok

Environment Variables

  • Server/SSR: process.env.MY_VAR
  • Client: import.meta.env.VITE_MY_VAR

Docs

  • AGENTS.md
  • docs/ai/README.md
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. yesterday First seen · 27 lines · 177 tokens per session scan A 984ca1ba3706

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository bskimball/tanstack-hono (118 stars, last pushed 21d ago), licensed MIT. It adds 177 tokens to every session, about $0.0009 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-30.