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 agentmods add skills/pymodel/react-frontend-skills/vitestnpx skills add PyModel/react-frontend-skills --skill vitestgit clone --depth 1 https://github.com/PyModel/react-frontend-skillsWhat 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 | $0.00046 | $0.01228 |
| Opus 5 | $0.00023 | $0.00614 |
| Sonnet 5 | $0.00009 | $0.00246 |
| Haiku 4.5 | $0.00005 | $0.00123 |
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 3d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vitest Best Practices
Vitest 4-compatible testing guide with 44 rules across 8 categories. Vitest 4 requires Node.js 20+ and Vite 6+ when used with Vite.
When to Apply
Reference these guidelines when:
- Writing new Vitest tests
- Debugging flaky or slow tests
- Setting up test configuration
- Reviewing test code in PRs
- Migrating from Jest to Vitest
- Optimizing CI/CD test performance
Jest-specific APIs and configuration outside documented migration differences are out of scope; use Jest's own documentation for tests that still run under Jest.
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Async Patterns | CRITICAL | async- |
| 2 | Test Setup & Isolation | CRITICAL | setup- |
| 3 | Mocking Patterns | HIGH | mock- |
| 4 | Performance | HIGH | perf- |
| 5 | Snapshot Testing | MEDIUM | snap- |
| 6 | Environment | MEDIUM | env- |
| 7 | Assertions | LOW-MEDIUM | assert- |
| 8 | Test Organization | LOW | org- |
Quick Reference
1. Async Patterns (CRITICAL)
async-await-assertions- Await async assertions to prevent false positivesasync-return-promises- Return promises from test functionsasync-fake-timers- Use fake timers for time-dependent codeasync-waitfor-polling- Use vi.waitFor for async conditionsasync-concurrent-expect- Use test context expect in concurrent testsasync-act-wrapper- Await user events to avoid act warningsasync-error-handling- Test async error handling properly
2. Test Setup & Isolation (CRITICAL)
setup-beforeeach-cleanup- Clean up state in afterEach hookssetup-restore-mocks- Restore mocks after each testsetup-avoid-shared-state- Avoid shared mutable state between testssetup-beforeall-expensive- Use beforeAll for expensive one-time setupsetup-reset-modules- Reset modules when testing module statesetup-test-factories- Use test factories for complex test data
3. Mocking Patterns (HIGH)
What ships with it
45 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.
- AGENTS.md 8.7 KB
- references/assert-edge-cases.md 2.3 KB
- references/assert-expect-assertions.md 2.3 KB
- references/assert-one-assertion-concept.md 2.6 KB
- references/assert-specific-matchers.md 2.1 KB
- references/assert-toequal-vs-tobe.md 2.1 KB
- references/async-act-wrapper.md 2.4 KB
- references/async-await-assertions.md 1.3 KB
- references/async-concurrent-expect.md 1.9 KB
- references/async-error-handling.md 2.1 KB
- references/async-fake-timers.md 2.0 KB
- references/async-return-promises.md 1.5 KB
- references/async-waitfor-polling.md 1.8 KB
- references/env-browser-api-mocking.md 2.2 KB
- references/env-globals-config.md 1.8 KB
- references/env-per-file-override.md 2.4 KB
- references/env-setup-files.md 2.3 KB
- references/mock-avoid-overmocking.md 2.8 KB
- references/mock-clear-between-tests.md 2.1 KB
- references/mock-implementation-not-value.md 2.3 KB
- references/mock-msw-network.md 2.6 KB
- references/mock-spyon-vs-mock.md 2.4 KB
- references/mock-type-safety.md 2.4 KB
- references/mock-vi-mock-hoisting.md 2.1 KB
- references/org-describe-nesting.md 2.4 KB
- references/org-file-colocation.md 1.7 KB
- references/org-test-naming.md 2.0 KB
- references/org-test-skip-only.md 1.8 KB
- references/perf-bail-fast-fail.md 1.7 KB
- references/perf-disable-isolation.md 2.0 KB
- references/perf-happy-dom.md 2.3 KB
- references/perf-pool-selection.md 2.0 KB
- references/perf-run-mode-ci.md 1.6 KB
- references/perf-sharding.md 2.0 KB
- references/setup-avoid-shared-state.md 2.5 KB
- references/setup-beforeall-expensive.md 2.3 KB
- references/setup-beforeeach-cleanup.md 1.9 KB
- references/setup-reset-modules.md 2.5 KB
- references/setup-restore-mocks.md 2.1 KB
- references/setup-test-factories.md 2.8 KB
- references/snap-avoid-large.md 2.3 KB
- references/snap-describe-intent.md 2.1 KB
- references/snap-inline-over-file.md 1.9 KB
- references/snap-review-updates.md 1.8 KB
- references/snap-stable-serialization.md 2.3 KB
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.
- 3d ago First seen · 121 lines · 46 tokens per session scan A 353024b8238f
vitest is a skill published in the GitHub repository PyModel/react-frontend-skills (3 stars, last pushed 13d ago), licensed MIT. It adds 46 tokens to every session and 1,228 once invoked, about $0.0002 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-31.
Other skills, from other repositories
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
backend/testing-guide
后端测试编写指南,包括单元测试、集成测试和E2E测试的编写方法和最佳实践.
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
unit-test-generator
Automatically generate unit tests based on source code, supporting multiple languages and testing frameworks.
claude-code-qa
The complete QA skill for Claude Code — turn Claude into an expert QA engineer that picks the right test type, writes reliable Playwright, Cypress, and pytest tests, eliminates flaky tests, enforces coverage, and wires up CI. Claude Code QA testing done right.
vc-web-testing
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.