vite

Project rules for using Vite, a frontend build tool and development server, when the repository is configured for it. They describe the expected entry points, environment variables, aliases, rendering model, and tests.

In plain words
What is it for?
Use them when editing a Vite project’s frontend, configuration, environment variables, routes, aliases, server rendering setup, or tests.
Why use it?
They prevent code from importing conventions belonging to other frameworks, such as Next.js, and keep changes aligned with the actual Vite setup.

Cursor rule

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/kleosr/kleosrules/vite
Clone the repo
git clone --depth 1 https://github.com/kleosr/kleosrules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 276 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00276
Opus 5 $0.00000 $0.00138
Sonnet 5 $0.00000 $0.00055
Haiku 4.5 $0.00000 $0.00028

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

Security

Grade A, and why

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

shared/rules/vite.mdc · 22 lines

What it actually says

Vite

Only if package.json has vite and not next. If both, Next wins. Do not import next/navigation, next/image, or getServerSideProps.

Read vite.config.* and neighbors. Entry is index.html + src/main.* unless this config says otherwise.

Hard

  • Env: import.meta.env (VITE_ prefix for public). Do not invent Next NEXT_PUBLIC_* here.
  • Client SPA by default. No RSC, no app/ router conventions, no Server Components.
  • SSR only if a plugin in this config already does it (vike, vite-plugin-ssr). Match that plugin. Do not invent Next loading.tsx.
  • Aliases and base from this Vite config, not from Next basePath.
  • Tests: Vitest if vitest is a dependency. pnpm.

Subagents inherit this. Do not paste into Task prompts.

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 · 22 lines · 0 tokens per session scan A 27a804a0d7ce

Subscribe to this mod's changes

vite is a cursor rule published in the GitHub repository kleosr/kleosrules (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 276 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-31.