Borrowing it
Nothing to install: this file belongs to ASDAlexey/vitest-auto-spy. 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/ASDAlexey/vitest-auto-spy/master/CLAUDE.mdgit clone --depth 1 https://github.com/ASDAlexey/vitest-auto-spyWrote 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/asdalexey/vitest-auto-spy/claude-md)<a href="https://agentmods.dev/instructions/asdalexey/vitest-auto-spy/claude-md"><img src="https://agentmods.dev/badge/instructions/asdalexey/vitest-auto-spy/claude-md/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/instructions/asdalexey/vitest-auto-spy/claude-md"><img src="https://agentmods.dev/badge/instructions/asdalexey/vitest-auto-spy/claude-md.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.00370 | $0.00370 |
| Opus 5.5 | $0.00148 | $0.00148 |
| Sonnet 5.5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
vitest-auto-spy 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 1mo 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.
What it actually says
vitest-auto-spy — instructions for AI coding agents
This file exists only because Claude Code discovers repository instructions from CLAUDE.md. It is a
pointer and nothing else, so it cannot disagree with the files it points at.
- Working on this repository — the library's source, its tests, its docs? Read
CONTRIBUTING.md: the commands, the gate, every surface a change has to reach, and the release flow. - Writing tests with the library in some other project? Read
AGENTS.md, the reference that ships in the npm package: a short map, with one file per topic inagent-docs/.
Three things worth knowing before you start, because they are the ones that cost time:
- Never commit, push or tag. The maintainer does that by hand.
npm run checkis the gate, and thecheckscript inpackage.jsonis the one list of what it runs;CONTRIBUTING.mdexplains each step. A change is not finished until it passes.- The landing cards in
docs-site/index.mdare prose inside YAML. A:in an unquoteddetails:ortitle:value ends the value and starts a new key, and the only thing that reads that frontmatter isvitepress build— in the pages workflow, after the gate, so it fails onmasterwith the deploy already red. Write a semicolon or a dash instead, and runnpm run docs:checkafter touching any frontmatter underdocs-site/.
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.
- 1mo ago Changed · -2 lines · -42 tokens per session 2e2eaac0719a
- 1mo ago Changed · +2 lines · +38 tokens per session a4e0be3f6652
- 1mo ago Changed · +6 lines · +145 tokens per session f4ddc130a3fd
- 1mo ago First seen · 17 lines · 229 tokens per session scan A 48b3770e7749
vitest-auto-spy CLAUDE.md is an instructions file published in the GitHub repository ASDAlexey/vitest-auto-spy (10 stars, last pushed yesterday), licensed MIT. It adds 370 tokens to every session, about $0.0015 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-31.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.