vite

A front-end development tool for running a local development server and packaging web applications for release. It includes configuration, plugins, environment settings, server-side rendering, and fast updates while editing files.

In plain words
What is it for?
Use it to start or configure a Vite project, manage plugins and environment variables, work with live browser updates, and build or deploy a site.
Why use it?
It provides the project setup and build process needed to develop and prepare modern front-end applications.

Skill for Claude CodeCodex

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 skills/itechmeat/llm-code/vite
Any agent
npx skills add itechmeat/llm-code --skill vite
Clone the repo
git clone --depth 1 https://github.com/itechmeat/llm-code

Made for: Claude Code, Codex.

Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,832 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.00080 $0.01832
Opus 5 $0.00040 $0.00916
Sonnet 5 $0.00016 $0.00366
Haiku 4.5 $0.00008 $0.00183

Measured 2d ago against content hash c7aaa1551060, 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.

skills/vite/SKILL.md · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vite

Quick navigation

  • Getting started: references/getting-started.md
  • Philosophy and rationale: references/philosophy.md, references/why-vite.md
  • Features: references/features.md
  • CLI: references/cli.md
  • Plugins (usage): references/using-plugins.md
  • Plugin API: references/api-plugin.md
  • HMR API: references/api-hmr.md
  • JavaScript API: references/api-javascript.md
  • Config reference: references/config.md
  • Dependency optimization: references/dep-pre-bundling.md
  • Assets: references/assets.md
  • Build: references/build.md
  • Static deploy: references/static-deploy.md
  • Env & modes: references/env-and-mode.md
  • SSR: references/ssr.md
  • Backend integration: references/backend-integration.md
  • Troubleshooting: references/troubleshooting.md
  • Performance: references/performance.md
  • Rolldown: references/rolldown.md
  • Migration: references/migration.md
  • Breaking changes: references/breaking-changes.md
  • Environment API: references/api-environment.md
  • Environment instances: references/api-environment-instances.md
  • Env plugins: references/api-environment-plugins.md
  • Env frameworks: references/api-environment-frameworks.md
  • Env runtimes: references/api-environment-runtimes.md

Core rules

  • Prefer minimal configuration; extend only as needed.
  • Keep index.html as a first-class entry point when using Vite defaults.
  • Treat dev server settings and build settings separately.
  • Document mode-dependent behavior for env variables and define.
  • Use future config to opt-in to deprecation warnings before migration.

Recipes

  • Scaffold a project with npm create vite@latest.
  • Configure aliases, server options, and build outputs in vite.config.*.
  • Load .env values into config with loadEnv when config needs them.
  • Add plugins with plugins: [] and define apply or enforce when needed.
  • Use HMR APIs for fine-grained updates when plugin or framework needs it.
  • Use optimizeDeps.include/exclude when deps aren't discovered on startup.
  • Use build.rollupOptions.input for multi-page apps.
  • Use the top-level input option to declare the entry once for apps without index.html; it feeds build.rolldownOptions.input, build.lib.entry, build.ssr, and optimizeDeps.entries by default.
  • Enable deprecation warnings: future: { removeSsrLoadModule: 'warn' }.
  • Use hotUpdate hook instead of handleHotUpdate for environment-aware HMR.
  • Use this.environment instead of options.ssr in plugin hooks.

Read the full file on GitHub · 107 lines

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 · 107 lines · 80 tokens per session scan A c7aaa1551060

Subscribe to this mod's changes

vite is a skill published in the GitHub repository itechmeat/llm-code (22 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 1,832 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens