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 review-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/review-vitest)<a href="https://agentmods.dev/skills/louisbrulenaudet/monorepo-template/review-vitest"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-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/review-vitest"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-vitest.svg" alt="Reviewed on agentmods" width="80" 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.00070 | $0.01010 |
| Opus 5 | $0.00035 | $0.00505 |
| Sonnet 5 | $0.00014 | $0.00202 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
review-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 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.
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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Vitest
Review the Vitest setup for alignment with current official Vitest and Cloudflare Workers testing best practices - shared config correctness, pool selection, agent-friendly output, and the repo's unit/integration testing split. Your reply must be a plan of suggested changes: concise, actionable, structured - not only prose.
Invocation
Text after the slash command is additional scope/focus (e.g. "workers pool only", "reporters") - narrow the review accordingly.
Ground truth (mandatory)
Your pre-trained knowledge of Vitest may be outdated. Do not draft suggestions from memory alone.
- Resolve "Vitest" via the Context7 MCP (
resolve-library-id→query-docs) at v4: config API (mergeConfig/defineConfig), pool options (threads/forks/vmThreads), reporter list (including agent-aware auto-detection), project/workspace patterns, experimental flags validity. - Also resolve "@cloudflare/vitest-plugin" (or "Cloudflare Workers" docs) for current Workers-pool guidance; prefer the cloudflare-docs MCP for Workers testing questions.
- For anything Context7 lacks, use Firecrawl search/scrape restricted to official domains (
vitest.dev,developers.cloudflare.com/workers/testing/) - vitest config reference, Workers testing guide,createTestHarness()reference. - Version currency: catalog
vitest,@cloudflare/vitest-pluginin pnpm-workspace.yaml vs latest stable; flag deprecated config keys still present in presets or per-app configs. - Cite the retrieved source next to every finding; label anything unverifiable as Unverified.
Scope artifacts
- packages/vitest-config/src/index.ts (
defineNodeConfig) and src/workers.ts (defineWorkersConfig) - Per-app configs: apps/front-app/vitest.config.ts, apps/worker-api/vitest.config.mts
- Suites under
apps/*/tests/; repo testing-split policy (root +packages/vitest-config/AGENTS.md) - Root scripts
test/test:watchturbo wiring
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 First seen · 62 lines · 70 tokens per session scan A 39883049c6bc
review-vitest is a skill published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 11d ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,010 once invoked, about $0.0003 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-30.
Other skills, from other repositories
character-animation-qa
Review local character animation with schema checks, Playwright browser previews, frame sampling, and FFmpeg/ffprobe final output checks.
Edge Computing Testing
Testing edge computing deployments including latency verification, edge function testing, CDN worker testing, and geo-distributed test execution.
agent-evaluation
Evaluate and improve Claude Code commands, skills, and agents. Use when testing prompt effectiveness, validating context engineering choices, or measuring improvement quality.
do-and-judge
Execute a task with sub-agent implementation and LLM-as-a-judge verification with automatic retry loop.
test-coverage
Use after writing tests to assess coverage quality across structural, mutation, requirements, and API/integration dimensions; organized knowledge for choosing and interpreting coverage analyses.
design-testing-strategy
Use before writing any type of tests. Distills 14 industry sources into deterministic decision gates, schemas, and worked test examples.