Borrowing it
Nothing to install: this file belongs to djankies/vitest-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/djankies/vitest-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/djankies/vitest-mcpWrote 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/instructions/djankies/vitest-mcp/claude-md)<a href="https://agentmods.dev/instructions/djankies/vitest-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/djankies/vitest-mcp/claude-md.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.01227 | $0.01227 |
| Opus 5 | $0.00613 | $0.00613 |
| Sonnet 5 | $0.00245 | $0.00245 |
| Haiku 4.5 | $0.00123 | $0.00123 |
Grade A, and why
vitest-mcp CLAUDE.md 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 8d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a Model Context Protocol (MCP) server that provides AI-optimized Vitest testing tools. The server offers structured JSON output, intelligent test targeting, coverage analysis, and safety guards to prevent accidental full test suite runs.
Development Commands
Building and Development
npm run build- Compile TypeScript to JavaScript indist/folder and make executablenpm run dev- Watch mode compilation with TypeScriptnpm start- Run the compiled MCP servernpm run lint- Run ESLint on TypeScript source filesnpm test- Run the project's own test suite using Vitestnpm run prepare- Build before publishing (runs automatically on install)
Development Mode (Self-Testing)
When developing the MCP server itself, you can enable development mode to test it on its own repository:
-
Set the environment variable in
.env.development:VITEST_MCP_DEV_MODE=true -
Build and run the server:
npm run build npm start -
Use the tools on the repository itself:
set_project_root({ path: "/path/to/vitest-mcp" }) // Now allowed in dev mode run_tests({ target: "./src/tools" })
This bypasses the self-protection check that normally prevents the MCP server from running on itself.
Testing Commands
- IMPORTANT: Always use the project's own MCP tools for testing, not raw vitest commands
set_project_root({ path: "/absolute/path/to/project" })- Required first steprun_tests({ target: "./src/components", format: "detailed" })- Run specific testsanalyze_coverage({ target: "./src", threshold: 80 })- Coverage analysislist_tests({ directory: "./src" })- Find test files
Single Test Execution
When working on a specific test file, use:
run_tests({
target: "./src/tools/__tests__/list-tests.test.ts",
format: "detailed"
})
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.
- 8d ago First seen · 176 lines · 1,227 tokens per session scan A f3ae4e7cb3c3
vitest-mcp CLAUDE.md is an instructions file published in the GitHub repository djankies/vitest-mcp (17 stars, last pushed 10mo ago), licensed MIT. It adds 1,227 tokens to every session, about $0.0061 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.