Borrowing it
Nothing to install: this file belongs to LiveTrack-X/spec-driven-ai-development. 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/LiveTrack-X/spec-driven-ai-development/main/adapters/github-copilot/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/LiveTrack-X/spec-driven-ai-developmentWrote 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/livetrack-x/spec-driven-ai-development/copilot-instructions)<a href="https://agentmods.dev/instructions/livetrack-x/spec-driven-ai-development/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/livetrack-x/spec-driven-ai-development/copilot-instructions/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/livetrack-x/spec-driven-ai-development/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/livetrack-x/spec-driven-ai-development/copilot-instructions.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.01138 | $0.01138 |
| Opus 5.5 | $0.00455 | $0.00455 |
| Sonnet 5.5 | $0.00228 | $0.00228 |
| Haiku 4.5 | $0.00114 | $0.00114 |
Grade A, and why
spec-driven-ai-development copilot-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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDAD Protocol
Status: Active Scope: GitHub Copilot project instructions
SDAD (SPEC-Directed AI Development) is a method-agnostic, repository-local operating protocol for AI-assisted development, not a coding method, agent runtime, or substitute for owner evidence.
Fast Start
- Read
sdad-state.yaml: scale, packet, gates, validation, eligible routes. - Read
docs/INDEX.mdas a router. - Inspect current source and tests. Current intent selects the routed path, heading, active section, or targeted match; membership does not mean read the whole file.
- History on demand;
docs/Repository-Operating-Rules.mdheadings for policy/risk.
Controls And Route
Use Plan -> Route -> Implement -> Verify -> Report; gates and handoffs are triggered. For read-only/planning work, omit phase N/A lists; never claim evidence from skipped work. Before implementation, compare requested outcomes/constraints with the plan.
Controls: scale, execution_scope: unit | packet, owner gates. Mini: one unit;
Standard: one packet; Full: gates. Ask-first means no authorization.
Multi-packet needs an approved list, never session scope. routed_docs permits
selection, not authority/full read.
Infer intent via INDEX. Inspect evidence before asking; ask one blocking question only for an unresolved material direction, authority, scope, gate, or claim. Review/audit is read-only unless the owner authorizes changes. On resume, verify a declared handoff; if absent, recover from state -> INDEX -> current source/tests.
On a current owner instruction redirect, stop affected local/delegated work, re-enter Plan/Route, reconcile SPEC/state and affected TODO/evidence. Old-boundary outputs stay stale until revalidated. A clear action request authorizes its named action/boundary; persist it, do not re-ask. Information questions, hypotheticals, quotations, and negations are not authorization. Prerequisites, tool policy, and gates remain.
Inspect current owner-named input even if routed_docs omits it; reconcile state/routes
before implementing adopted input.
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 · -7 lines · -77 tokens per session 0cb0d19f3e30
- 1mo ago First seen · 113 lines · 1,215 tokens per session scan A ee914a5ebaa5
spec-driven-ai-development copilot-instructions.md is an instructions file published in the GitHub repository LiveTrack-X/spec-driven-ai-development (4 stars, last pushed 1mo ago), licensed MIT. It adds 1,138 tokens to every session, about $0.0046 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.