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.
npx skills add magnus919/agent-skills --skill vitegit clone --depth 1 https://github.com/magnus919/agent-skillsWrote 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/skills/magnus919/agent-skills/vite)<a href="https://agentmods.dev/skills/magnus919/agent-skills/vite"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/vite/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/skills/magnus919/agent-skills/vite"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/vite.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00104 | $0.01228 |
| Opus 5 | $0.00052 | $0.00614 |
| Sonnet 5 | $0.00021 | $0.00246 |
| Haiku 4.5 | $0.00010 | $0.00123 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vite Operations
Use this skill for the Vite toolchain itself: project discovery, config and plugin behavior, environment loading, dev-server diagnostics, production builds, and asset/deployment boundaries. Keep application architecture and UI implementation with frontend-engineering, infrastructure and CI design with platform-engineering, browser tests with playwright, and accessibility implementation/review with web-accessibility.
Operating contract
- Discover before changing. Read
package.json, lockfile,vite.config.*,tsconfig*.json, scripts, framework plugin, and deployment assumptions. Identify the package manager from the lockfile; do not invent a command. - Check the actual toolchain. Run
scripts/vite-doctor --jsonfrom this skill or the project root to capture Node, package-manager, Vite package, config, and environment evidence. A Vite version in documentation is not proof of the installed version. - Keep configuration explicit. Review
root,base,resolve.alias, plugins,server.host/port,preview,build.outDir,build.rollupOptions, anddefine. Treatdefineandimport.meta.envas compile-time/public data; never place secrets inVITE_*variables or client bundles. - Build before claiming success. Use the project's existing script (normally
npm run build,pnpm build,yarn build, orbun run build) with a bounded timeout. Inspect output files and warnings, then exercise the built app at its deployed base path when possible. - Treat mutations as gated. Read-only discovery may proceed. Before installing packages, editing config, deleting output, starting a server, or changing deployment settings, confirm the target, scope, and rollback path. Prefer a new output directory or version-controlled change and never overwrite a user's uncommitted work.
- Keep evidence bounded. Summarize logs and errors; do not paste
.envcontents, tokens, full bundles, or generated dependency trees.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 59 lines · 104 tokens per session scan A db87dd6ce09d
vite is a skill published in the GitHub repository magnus919/agent-skills (76 stars, last pushed yesterday), licensed MIT. It adds 104 tokens to every session and 1,228 once invoked, about $0.0005 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-09-05.
Other skills, from other repositories
qa
QA test your code changes by reading your git diff, choosing the right validation path for frontend/browser and backend changes, and reporting pass/fail with evidence.
gpt-tasteskill
Use this skill for premium frontend interfaces that require GSAP scroll animations, mathematically verified bento grids, and award-quality design. The most demanding taste variant.
stitch-skill
Use this skill when generating DESIGN.md files for Google Stitch, or when creating agent-friendly design specifications that will drive multi-step UI generation. Translates premium design principles into semantic design language.
brutalist-skill
Use this skill when the task calls for raw, mechanical, data-heavy interfaces with terminal aesthetics. Synthesizes Swiss typographic modernism with aerospace/military terminal design.
soft-skill
Use this skill when the task calls for an agency-tier, editorial, or luxury aesthetic. Produces premium interfaces with micro-interactions, spatial rhythm, and cinematic motion.
taste-skill
Use this skill when the task involves building or improving any web UI, frontend component, dashboard, or landing page. Enforces high-end design standards and eliminates generic AI-generated interface patterns.