Borrowing it
Nothing to install: this file belongs to kasuken/vscode-copilot-insights. 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/kasuken/vscode-copilot-insights/main/.github/instructions/repo-validation.instructions.mdgit clone --depth 1 https://github.com/kasuken/vscode-copilot-insightsWrote 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/kasuken/vscode-copilot-insights/repo-validation)<a href="https://agentmods.dev/instructions/kasuken/vscode-copilot-insights/repo-validation"><img src="https://agentmods.dev/badge/instructions/kasuken/vscode-copilot-insights/repo-validation/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/kasuken/vscode-copilot-insights/repo-validation"><img src="https://agentmods.dev/badge/instructions/kasuken/vscode-copilot-insights/repo-validation.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.00265 | $0.00265 |
| Opus 5 | $0.00133 | $0.00133 |
| Sonnet 5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
Repo Validation Workflow 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 9d 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
Repo Validation Workflow
- Treat
npm run compileas the required production validation gate for extension changes. It runs asset copying,tsc --noEmit, ESLint, and esbuild. - Run
npm run compile-testswhen changing tests or logic that extension tests import. It emits the CommonJSout/tree used by the VS Code test harness. - Start with the narrowest relevant behavior check, then broaden only when the changed surface warrants it.
- Remember that
npm testuses@vscode/test-electronand can download a full VS Code build. If the Electron harness is blocked or too slow, runnpm run compileandnpm run compile-tests, then clearly report that extension-host behavior remains unverified. - Do not delete
out/while a watch or compiler task is running. Re-runnpm run compileor stop the watcher before cleaning generated output.
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.
- 9d ago First seen · 13 lines · 265 tokens per session scan A 3cb4ce9c8645
Repo Validation Workflow is an instructions file published in the GitHub repository kasuken/vscode-copilot-insights (37 stars, last pushed 27d ago), licensed MIT. It adds 265 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
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
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).