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 itechmeat/llm-code --skill vitestgit clone --depth 1 https://github.com/itechmeat/llm-codeWrote 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/itechmeat/llm-code/vitest)<a href="https://agentmods.dev/skills/itechmeat/llm-code/vitest"><img src="https://agentmods.dev/badge/skills/itechmeat/llm-code/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/itechmeat/llm-code/vitest"><img src="https://agentmods.dev/badge/skills/itechmeat/llm-code/vitest.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.00073 | $0.02113 |
| Opus 5.5 | $0.00029 | $0.00845 |
| Sonnet 5.5 | $0.00015 | $0.00423 |
| Haiku 4.5 | $0.00007 | $0.00211 |
Grade A, and why
vitest 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 24d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vitest
Next generation testing framework powered by Vite.
Quick Navigation
- Test API - test, describe, hooks
- Expect API - matchers and assertions
- Mocking - vi.fn, vi.mock, fake timers
- Configuration - vitest.config.ts options
- CLI - command line reference
- Browser Mode - real browser testing
When to Use
- Testing Vite-based applications (shared config)
- Need Jest-compatible API with native ESM support
- Component testing in real browser
- Fast watch mode with HMR
- TypeScript testing without extra config
- Parallel test execution
Installation
Install: npm install -D vitest. Requires Node.js >=22 and Vite >=6.4 in v5.
Release Highlights (5.0.0)
- Requirements: Node.js >=22 and Vite >=6.4 are required.
@vitest/runneris inlined (the package is no longer published) andexpectis inlined, so old entry points were removed. - Mock/timer behavior: mocks are cleared by default before each test, and
Temporalcan now be mocked (with or without fake timers). - Replaced APIs:
sequentialtest/suite options are removed in favor ofconcurrent; thewebdriveriobrowser provider is removed;toHaveTextContentis strict withtoMatchTextContentas the alternative;expect.pollfails when the function does not resolve in time. - New defaults/outputs:
attachmentsDirdefaults to.vitest/attachments/(was.vitest-attachments/), and blob/json/junit/html reporter outputs default to.vitest; acreateReportAPI and.vitestreport directory convention are introduced. - Projects: inline projects extend the root config by default, nested projects are supported, distinct projects share one Vite server, and the config file is no longer looked up from ancestor directories (parent dirs no longer apply).
- Browser: locator objects replace locator strings,
locators.exactis on by default, and ascreenshotDirectoryconfig controlstoMatchScreenshotoutput. - Misc: benchmark public API was rewritten with a pluggable provider API;
-pis a shorthand for--project;-tuses>as separator; coveragethresholds.perFileaccepts an object and TypeScript build mode /vitest liststatic parsing are supported.
What ships with it
6 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.
- 24d ago Changed ba13db2c4eb8
- 1mo ago Changed · +10 lines 98dfccf39022
- 1mo ago First seen · 309 lines · 73 tokens per session scan A 9bb3b97784af
vitest is a skill published in the GitHub repository itechmeat/llm-code (24 stars, last pushed 24d ago), licensed MIT. It adds 73 tokens to every session and 2,113 once invoked, about $0.0003 per session on Opus 5.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
typescript
TypeScript strict mode with eslint and jest.
vitest-skill
Generates Vitest tests in JavaScript/TypeScript with Vite-native speed. Jest-compatible API with ESM support and HMR. Use when user mentions "Vitest", "vi.mock", "vitest.config". Triggers on: "Vitest", "vi.mock", "vi.fn", "Vite test", "vitest config".
jest-unit
Unit testing skill using Jest for TypeScript and JavaScript, covering mocking, spies, snapshots, coverage, async testing, and custom matchers.
Jasmine Testing
BDD-style JavaScript testing with Jasmine covering spies, async patterns, custom matchers, clock manipulation, and comprehensive test organization for frontend and Node.js applications.
jest
Jest testing best practices for JavaScript and TypeScript applications, covering test structure, mocking, and assertion patterns.
typescript-testing
Applies repository-aware TypeScript test design, behavior evidence, isolation, and mock-boundary criteria. Use when writing or reviewing unit tests.