Borrowing it
Nothing to install: this file belongs to pplancq/copilot-instructions. 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/pplancq/copilot-instructions/main/.github/instructions/vitest.instructions.mdgit clone --depth 1 https://github.com/pplancq/copilot-instructionsWrote 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/pplancq/copilot-instructions/vitest)<a href="https://agentmods.dev/instructions/pplancq/copilot-instructions/vitest"><img src="https://agentmods.dev/badge/instructions/pplancq/copilot-instructions/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/instructions/pplancq/copilot-instructions/vitest"><img src="https://agentmods.dev/badge/instructions/pplancq/copilot-instructions/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.01094 | $0.01094 |
| Opus 5.5 | $0.00438 | $0.00438 |
| Sonnet 5.5 | $0.00219 | $0.00219 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
copilot-instructions vitest.instructions.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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vitest Testing Instructions (Front)
Purpose
Ensure the quality, readability, maintainability, and accessibility of unit and integration tests in the front-end with Vitest, following the project's best practices.
Structure and Organization
- Tests must be placed in the
testsfolder at the same level assrc, following the same directory structure as the source code. For example, if a component is located atsrc/components/Button.tsx, its test must be placed attests/components/Button.test.tsx. - The test file name must follow the format:
<ComponentOrFunctionName>.test.ts(x). - Tests must always be grouped in a
describe, with sub-describeblocks if needed (maximum 2 levels). - Each test must use the format:
it('should ...', () => { ... }). - Tests and examples must always be written in English.
Imports and Tools
- Always explicitly import Vitest functions (
describe,it,expect, etc.). - Always use
userEventfrom Testing Library to simulate user interactions. - Always prefer
getByRolequeries with the associated label name to target elements. - Always use available accessibility assertions (
toHaveAccessibleName,toBeInTheDocument,toBeVisible,toHaveAccessibleDescription,toHaveAccessibleErrorMessage, etc.) to check element accessibility. - Always use
toHaveAccessibleNameto check accessibility links if available.
Accessibility (a11y)
- Systematically check accessibility points (a11y): presence of roles, labels, accessible error messages, etc.
- Check the visibility, validity, and accessibility of interactive elements.
- Tests must cover error and validation cases, ensuring messages are accessible (
aria-describedby,aria-invalid, etc.). - Always test keyboard navigation and the presence of landmarks (
banner,main,contentinfo, etc.). - Refer to RGAA and WCAG 2.2 instructions (see
.github/instructions/a11y.instructions.md).
API and Mocks
- For API calls, exclusively use MSW (Mock Service Worker).
- API mocks are placed in the folder:
<front project root>/mocks. - Only mock external dependencies (hooks, browser, etc.) when relevant for test isolation or stability. Avoid over-mocking.
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 First seen · 108 lines · 1,094 tokens per session scan A 88ecb0dd829b
copilot-instructions vitest.instructions.md is an instructions file published in the GitHub repository pplancq/copilot-instructions (4 stars, last pushed 8mo ago), licensed MIT. It adds 1,094 tokens to every session, about $0.0044 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.