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 Goldziher/ai-rulez --skill vite-plus-conventionsgit clone --depth 1 https://github.com/Goldziher/ai-rulezWrote 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/goldziher/ai-rulez/vite-plus-conventions)<a href="https://agentmods.dev/skills/goldziher/ai-rulez/vite-plus-conventions"><img src="https://agentmods.dev/badge/skills/goldziher/ai-rulez/vite-plus-conventions/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/goldziher/ai-rulez/vite-plus-conventions"><img src="https://agentmods.dev/badge/skills/goldziher/ai-rulez/vite-plus-conventions.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.00064 | $0.00582 |
| Opus 5 | $0.00032 | $0.00291 |
| Sonnet 5 | $0.00013 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
vite-plus-conventions 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 11d 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.
What it actually says
- Use vite+ as the unified TypeScript toolchain. It wraps best-in-class tools behind a single CLI. Configure your entire toolchain in
vite.config.tsby importingdefineConfigfromvite-plus. - Package manager: vite+ auto-detects from
package.jsonengine field or lockfile (pnpm-lock.yaml,yarn.lock,package-lock.json,bun.lock). Fallback ispnpm. Runvp install,vp add <pkg-name>orvp remove <pkg-name>for managing package dependencies. - Node manager: vite+ manages Node.js versions — replaces
nvm/fnm. Runvp env onthenvp env install <node-version>to install Node.js runtime. Runvp env pinto pin version. - Linter:
oxlintvia vite+ — a fast Rust-powered alternative to legacy JavaScript linters. Runvp lintfor linting with TypeScript-aware rules. - Formatter:
oxfmtvia vite+ — a fast alternative to legacy JavaScript formatters. Runvp fmtfor consistent code formatting. - Type checker:
oxlintwith type-aware linting via vite+ — replacestsc --noEmitfor lint-time type checks. Configure it by enabling bothlint.options.typeAwareandlint.options.typeCheckinvite.config.ts. Runvp lintfor type-aware linting. - Testing:
vitestvia vite+ — runvp testfor fast Vite-native testing with HMR, coverage, and snapshot support. Import fromvite-plus/testinstead ofvitestwhen writing tests. - Bundler:
rolldown(Rust-powered Rollup replacement) for Vite apps,tsdownfor library builds. Runvp buildfor Vite apps orvp packfor libraries. - Task runner: vite+ supports task caching for build pipelines. Define tasks in
vite.config.tsorpackage.jsonscripts and benefit from incremental builds by usingvp run <task-name>. - CI integration: use
vp lint,vp fmt,vp test --coverage,vp build/vp packin CI pipelines. - Migrate from existing tools: vite+ is a drop-in replacement. Run
vp migrateto migrate your entire toolchain to vite+.
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.
- 11d ago First seen · 17 lines · 64 tokens per session scan A 23982af65f33
vite-plus-conventions is a skill published in the GitHub repository Goldziher/ai-rulez (141 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 582 once invoked, about $0.0003 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.
Other skills, from other repositories
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
test-new-skill
Skill "test-new-skill" from dimetron/pi-go, covering test-new-skill, examples and guidelines.
softdev-loop
Go software-development loop — implement, test, vet; repeat until green.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…