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 sentimony/skills --skill vitestgit clone --depth 1 https://github.com/sentimony/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/sentimony/skills/vitest)<a href="https://agentmods.dev/skills/sentimony/skills/vitest"><img src="https://agentmods.dev/badge/skills/sentimony/skills/vitest/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/sentimony/skills/vitest"><img src="https://agentmods.dev/badge/skills/sentimony/skills/vitest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk 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.00066 | $0.04437 |
| Opus 5.5 | $0.00026 | $0.01775 |
| Sonnet 5.5 | $0.00013 | $0.00887 |
| Haiku 4.5 | $0.00007 | $0.00444 |
Grade B, and why
vitest scanned grade B with 1 finding 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 12d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Stale `.nuxt` state**: do not delete `.nuxt`/`node_modules/.cache/nuxt` blindly for a "clean" run; it breaks the tests' tsconfig resolution and adds noisy false signals. Regenerate with `npx nuxt prepare`, not a bare Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vitest
Use this skill to add, fix, or run Vitest tests without turning the task into a Vitest API reference lookup.
Helper Scripts Available:
scripts/inspect_vitest.py- Reports normalized package, runtime, configuration, framework, filesystem-candidate, and diagnostic signals without exposing repository-controlled textscripts/run_vitest.py- Runs Vitest through the detected package manager with useful defaults
<skill> means the path to this local skill folder. Run helper scripts with --help when usage is unclear or before first use in a session. Prefer using helper scripts as black-box tools. Read or modify their source only when debugging the skill itself or when behavior is unclear.
Decision Tree
User task -> Is this an existing project?
- Audit -> Read: references/audit.md
Run: python <skill>/scripts/inspect_vitest.py --root <project>
Collect evidence before proposing changes.
- Yes -> Run: python <skill>/scripts/inspect_vitest.py --root <project>
Use detected framework, config, aliases, and package manager.
- No / new setup -> Inspect package.json manually if present, then create the
smallest Vitest setup that matches the runtime.
Next -> What is under test?
- Node/library logic -> environment: node
- React/Vue/Svelte component -> environment: jsdom or happy-dom
- Nuxt/Vue app code -> prefer existing Nuxt/Vite test utilities and config
- Edge/Workers code -> match the project's existing worker test setup
- Browser-specific behavior -> consider Vitest browser mode only if already used
Then -> Write or fix one focused test, run it directly, then broaden only as needed.
Core Workflow
- Inspect first: discover existing scripts, config files, setup files, aliases, and test conventions.
- Match the project: use its package manager, test naming, setup file, mock style, and import aliases.
- Keep tests behavioral: assert public outcomes instead of private implementation details.
- Isolate state: reset mocks, timers, DOM, environment variables, and module state when the test mutates them.
- Verify narrowly first: run one file or name pattern before running the whole suite.
What ships with it
11 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.
- CHANGELOG.md 21 KB
- examples/node_function.test.ts 240 B runs code
- examples/react_component.test.tsx 416 B
- examples/vue_component.test.ts 347 B runs code
- LICENSE 1.0 KB
- references/audit.md 8.7 KB
- scripts/inspect_vitest.py 14 KB runs code
- scripts/node_environment.py 8.9 KB runs code
- scripts/run_vitest.py 29 KB runs code
- scripts/test_inspect_vitest.py 15 KB runs code
- scripts/test_run_vitest.py 60 KB runs code
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.
- 12d ago Changed · +3 lines bf2890be2dd7
- 13d ago Changed 8e6e113b3af8
- 15d ago Changed · -5 lines 49bc21561f4c
- 22d ago Changed · +1 lines ac79f0240245
- 1mo ago Changed · +4 lines 53f52170d0a9
- 1mo ago Changed · +2 lines 80a581e9c21f
- 1mo ago Changed · +8 lines 8bbdebfe412b
- 1mo ago First seen · 185 lines · 66 tokens per session scan B fbcda278b0bf
vitest is a skill published in the GitHub repository sentimony/skills (6 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 4,437 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
walkthrough
Generate a Phase-2 Walkthrough artifact (walkthrough.md) once implementation and verification are complete. Captures a Change Summary, Verification Steps (commands + unit tests + automated browser testing outcomes), Visual Proof (screenshots/recordings embedded directly in the file), and a Review Gate (final diff + PR…
aif-test
Run unit, integration, e2e and UI tests with coverage analysis, build verification, visual regression and QA reports.
csharp-mstest
Get best practices for MSTest 3.x/4.x unit testing, including modern assertion APIs and data-driven tests.
csharp-tunit
Get best practices for TUnit unit testing, including data-driven tests.
csharp-nunit
Get best practices for NUnit unit testing, including data-driven tests.
csharp-xunit
Get best practices for XUnit unit testing, including data-driven tests.