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 agentmods add instructions/bartstc/vite-ts-react-template/testsgit clone --depth 1 https://github.com/bartstc/vite-ts-react-templateWhat 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 | $0.00264 | $0.00264 |
| Opus 5 | $0.00132 | $0.00132 |
| Sonnet 5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
vite-ts-react-template tests.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 2d 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
Testing
Tools
| Type | Location | Tool |
|---|---|---|
| Unit | .test.ts / .test.tsx beside src |
Vitest |
| Storybook | .stories.tsx beside components |
Storybook |
| E2E | e2e/ directory |
Playwright |
| API mocking | test-lib/handlers/ |
MSW |
| Fixtures | test-lib/fixtures/ |
Custom |
AI Boundaries
- Generate new test files and business logic freely
- Modify existing tests when change is mechanical (renames, API updates, imports, type fixes). Ask first when change alters intent — assertions, setup, scenario, or expectations
- Never delete a test without explicit request
- Analyze test failures to help debug
Test Priorities
- Prioritize: happy path with realistic data, user-facing error conditions, edge cases affecting business logic
- Each test verifies distinct behavior — avoid multiple variations triggering the same code path
- Skip redundant cases: empty arrays when "not found" is covered,
undefinedwhen types prevent it
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.
- 2d ago First seen · 29 lines · 264 tokens per session scan A 4b3fd881446f
vite-ts-react-template tests.instructions.md is an instructions file published in the GitHub repository bartstc/vite-ts-react-template (121 stars, last pushed 1mo ago), licensed MIT. It adds 264 tokens to every session, about $0.0013 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
omnigent copilot-instructions.md
Copilot instructions for omnigent-ai/omnigent, covering copilot code review instructions, e2e test requirement, backend test coverage and frontend test coverage.
Math-To-Manim tests.instructions.md
Guidelines for writing and maintaining tests in Math-To-Manim.
instrMCP CLAUDE.md
Instructions for caidish/instrMCP, covering claude.md, development commands, always use conda environment instrmcpdev for testing, unit tests (fast, no hardware required - all mocked) and e2e tests (requires playwright and browser automation).
copilot-instructions unit-and-integration-tests.instructions.md
Unit and integration testing best practices with pytest.
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).
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.