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 louisbrulenaudet/monorepo-template --skill front-vitestgit clone --depth 1 https://github.com/louisbrulenaudet/monorepo-templateWrote 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/louisbrulenaudet/monorepo-template/front-vitest)<a href="https://agentmods.dev/skills/louisbrulenaudet/monorepo-template/front-vitest"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/front-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/louisbrulenaudet/monorepo-template/front-vitest"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/front-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.00102 | $0.01380 |
| Opus 5.5 | $0.00041 | $0.00552 |
| Sonnet 5.5 | $0.00020 | $0.00276 |
| Haiku 4.5 | $0.00010 | $0.00138 |
Grade A, and why
front-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 28d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Front-app Vitest depth
Hard constraints and Node-first defaults live in the path-scoped rule .claude/rules/tests/front-react.md / .cursor/rules/tests/front-react.mdc. Load this skill only when you need harnesses beyond that rule.
Prerequisites
Installed in front-app (catalog deps): happy-dom, @testing-library/react, @testing-library/jest-dom, @testing-library/user-event, @testing-library/dom. jsdom is NOT installed - add it via the catalog only if one suite needs a per-file jsdom fallback for a happy-dom spec gap. Vitest bundles no DOM. Do not invent a DOM suite under plain Node.
Environment and setup
Keep package default environment node for existing Node suites. A DOM suite opts in per file with the control comment // @vitest-environment happy-dom on line 1 (installed default; jsdom only as a per-file fallback, see Prerequisites).
Setup file apps/front-app/vitest.setup.ts (wired via setupFiles): sets globalThis.IS_REACT_ACT_ENVIRONMENT = true for every suite, then behind a typeof document !== "undefined" guard imports @testing-library/jest-dom/vitest and registers afterEach(cleanup) - Node suites skip the harness entirely - Vitest globals are off, so RTL auto-cleanup never registers, and isolate: false would leak DOM state across files without it. React act requires that flag; see https://react.dev/reference/react/act .
Vitest config for JSX
A separate vitest.config.ts ignores vite.config.ts unless you mergeConfig https://vitest.dev/config/ . front-app's vitest.config.ts already loads @vitejs/plugin-react, so JSX/tsx suites work as-is.
Do not blindly mergeConfig the full apps/front-app/vite.config.ts - it loads cloudflare, prod env asserts, Devtools. Add only needed plugins. Never cloudflareTest on front-*. If adding the TanStack Router Vite plugin under Vitest, place it before react. Use #/* imports - never invent @/. Prefer vi.stubEnv over .env.production. Coverage is not configured for front-app - do not invent thresholds.
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.
- 28d ago Changed 634cf01e57cc
- 1mo ago Changed · -31 lines da4c9bbadfc9
- 1mo ago First seen · 129 lines · 102 tokens per session scan A 6ab2215a5fc4
front-vitest is a skill published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed today), licensed Apache-2.0. It adds 102 tokens to every session and 1,380 once invoked, about $0.0004 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
vitest
Set up Vitest testing in any project — detects type (Cloudflare Workers, React, Node, library), generates vitest.config.ts, test setup, utilities, and a sample test. Covers mocking patterns, coverage config, workspace setup, Jest migration. Use whenever the user mentions adding tests, setting up Vitest, configuring…
component-creation
Step-by-step workflow for creating accessible, tested UI components. Use when the user asks to create a new UI component.
testing-pyramid
Test Distribution Analysis Command 🧪.
component-test
Generate production-grade Vitest tests from HTML elements captured in DevTools. Two-phase workflow (analysis → generation) with edge case discovery.
frontend-testing
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.