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 punkadillo/figma-code-composer --skill vitest-testing-patternsgit clone --depth 1 https://github.com/punkadillo/figma-code-composerWrote 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/punkadillo/figma-code-composer/vitest-testing-patterns)<a href="https://agentmods.dev/skills/punkadillo/figma-code-composer/vitest-testing-patterns"><img src="https://agentmods.dev/badge/skills/punkadillo/figma-code-composer/vitest-testing-patterns.svg" alt="Measured on agentmods" height="20"></a>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.00025 | $0.02203 |
| Opus 5 | $0.00013 | $0.01102 |
| Sonnet 5 | $0.00005 | $0.00441 |
| Haiku 4.5 | $0.00003 | $0.00220 |
Grade A, and why
vitest-testing-patterns 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 4d 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.
This is a copy
95% identical to vitest-performance — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vitest testing patterns
Master Vitest testing patterns including unit tests, mocks, spies, and browser mode testing. This skill provides comprehensive coverage of essential concepts, patterns, and best practices for professional Vitest development.
Overview
Vitest is a powerful tool for typescript development, providing robust capabilities for maintaining code quality and ensuring reliable software delivery. This skill covers the fundamental through advanced aspects of working with Vitest.
Installation and Setup
Basic Installation
Setting up Vitest requires proper installation and configuration in your development environment.
# Installation command specific to Vitest
# Follow official documentation for latest version
Project Configuration
Create appropriate configuration files and setup for your project structure:
- Configuration file setup
- Project structure organization
- Team collaboration setup
- CI/CD integration preparation
Core Concepts
Fundamental Principles
Understanding the core principles of Vitest is essential for effective usage:
- Architecture - How Vitest is structured and operates
- Configuration - Setting up and customizing behavior
- Integration - Working with other tools and frameworks
- Best Practices - Industry-standard approaches
Key Features
Vitest provides several key features that make it valuable:
- Feature 1: Core functionality
- Feature 2: Advanced capabilities
- Feature 3: Integration options
- Feature 4: Performance optimization
- Feature 5: Extensibility
Configuration Strategy
Proper configuration ensures Vitest works optimally:
- Environment-specific setup
- Team standards enforcement
- Performance tuning
- Error handling configuration
Advanced Usage
For complex scenarios, Vitest offers advanced capabilities:
- Custom extensions
- Advanced patterns
- Performance optimization
- Scalability considerations
Code Examples
Example 1: Basic Setup
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.
- 4d ago First seen · 496 lines · 25 tokens per session scan A cf2c895f210a
vitest-testing-patterns is a skill published in the GitHub repository punkadillo/figma-code-composer (3 stars, last pushed 20d ago), licensed MIT. It adds 25 tokens to every session and 2,203 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to vitest-performance, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
testing-strategy
Comprehensive testing skill covering unit, integration, and e2e testing with TDD. Use when writing tests, improving coverage, or setting up testing infrastructure. Keywords: test, TDD, unit test, integration, e2e, coverage, mock, jest, vitest.
write-tests
Write Vitest unit/integration tests OR Playwright e2e tests for an existing source file (server action, page, component, query). Reads the project's wired test framework from .workflow/meta.json#stack.test, follows the mocking patterns already present in vitest.setup.ts and any sibling test files. Use when the user…
rn-write-tests
Use to write tests for an Expo + RN app: Jest + React Native Testing Library for unit/integration (components, hooks, queries, mutations) and Maestro for end-to-end flows (sign-in, navigation, forms). Sets up the testing stack on first call (jest-expo preset, RNTL, jest config) and writes a focused test next to the…
ios-testing-patterns
XCTest and XCUITest execution workflows and flaky test detection patterns.
test-generation-patterns
Use this skill when generating tests with AI assistance. Activate when the user wants to create unit tests, integration tests, generate test cases, improve test coverage, write tests for existing code, or set up testing patterns for their project.