Borrowing it
Nothing to install: this file belongs to FredAntB/Spec-Driven-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/FredAntB/Spec-Driven-Development/main/phase2c/flow_c/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/FredAntB/Spec-Driven-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/fredantb/spec-driven-development/copilot-instructions)<a href="https://agentmods.dev/instructions/fredantb/spec-driven-development/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/fredantb/spec-driven-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/fredantb/spec-driven-development/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/fredantb/spec-driven-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.00437 | $0.00437 |
| Opus 5.5 | $0.00175 | $0.00175 |
| Sonnet 5.5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
Spec-Driven-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.
What it actually says
GitHub Copilot Instructions
Project: Engineering Task Board — v1.0
═══════════════════════════════════════════════════════════ SPEC DRIVEN DEVELOPMENT — PROJECT CONSTITUTION Project: Engineering Task Board Version: v1.0
This project uses Spec Driven Development. All work is governed by three source-of-truth files:
requirements.md — What the system must do design.md — How the system is structured tasks.md — The ordered implementation plan
MANDATORY BEFORE ANY ACTION: 0. If CONTEXT.md exists, read it first — it has session state
- Read requirements.md in full
- Read design.md in full
- Read tasks.md — find the next incomplete [ ] task
HARD CONSTRAINTS:
- Implement ONLY what is in requirements.md
- Match EXACTLY the data model in design.md
- Create ONLY files listed or implied by design.md
- Never mark a task [x] without verifying its acceptance criterion
- If a requirement is ambiguous: ASK, do not guess
- If scope creep is detected: FLAG it, do not implement
AFTER COMPLETING A TASK:
- Run the verification step listed in tasks.md
- Mark the task [x] in tasks.md
- Report what was done and which REQ/NFR it satisfies
DIVERGENCE PROTOCOL: If implementation must deviate from design.md: 1. Stop immediately 2. Describe the conflict to the user 3. Wait for explicit approval to update design.md 4. Update design.md FIRST, then implement ═══════════════════════════════════════════════════════════
Copilot-Specific
- These instructions apply to Copilot Chat and inline completions.
- When generating code in a file, check whether that file is referenced in design.md before adding new exports or APIs.
- Do not propose dependencies that are absent from package.json / pyproject.toml without flagging the addition.
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 · 47 lines · 437 tokens per session scan A d3202d1f2c78
Spec-Driven-Development copilot-instructions.md is an instructions file published in the GitHub repository FredAntB/Spec-Driven-Development (155 stars, last pushed 5mo ago), licensed MIT. It adds 437 tokens to every session, about $0.0017 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-30.
Other instructions, from other repositories
plugin-files-mode
Rosetta Plugin Mode Bootstrap.
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).