Use it when changing agent prompts, instructions, templates, installation behavior, or README documentation, and when synchronizing the source files into client repositories.

It prevents maintainers from editing copied client files instead of the canonical templates and helps keep installations consistent and versionable.

spec-development-protocol copilot-instructions.md — Instructions file for GitHub Copilot by WojcikMM: A maintainer guide for the Spec Develo

Q: What is spec-development-protocol copilot-instructions.md?

A maintainer guide for the Spec Development Protocol, a reusable library of templates and instructions for software projects. It defines the source files, installation process, required change flow, and documentation updates.

Install

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.

agentmods

npx agentmods add instructions/wojcikmm/spec-development-protocol/copilot-instructions

Clone the repo

git clone --depth 1 https://github.com/WojcikMM/spec-development-protocol

Made for: GitHub Copilot.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/wojcikmm/spec-development-protocol/copilot-instructions.svg)](https://agentmods.dev/instructions/wojcikmm/spec-development-protocol/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/wojcikmm/spec-development-protocol/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/wojcikmm/spec-development-protocol/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>

Per session 694 This file is loaded in full into every session.

When invoked 694 The same file — it is already loaded in full.

Security scan A 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00694	$0.00694
Opus 5	$0.00347	$0.00347
Sonnet 5	$0.00139	$0.00139
Haiku 4.5	$0.00069	$0.00069

Measured 3d ago against content hash 86277bc731cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec-development-protocol copilot-instructions.md scanned grade A with 1 finding 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 3d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Keep installer dependencies minimal (`curl`, `tar`, POSIX-friendly shell usage where possible).

.github/copilot-instructions.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Copilot Maintainer Instructions - SDP Library

You are maintaining the Spec Development Protocol (SDP) template repository.

Repository Model

Source files for distribution are stored in .apm/.
Client projects must receive these files under .github/ after running install.sh.
This repository's own .github/ folder is for maintainer workflow and automation only.

Primary Goal

Keep the library consistent, versionable, and safe to reuse across projects. Every change must preserve the contract:

.apm/* is the canonical template source.
Installer copies .apm/* to client .github/*.

Change Flow (Required)

Identify the requested change and map it to one or more areas:
- Template content (.apm/agents, .apm/prompts, .apm/instructions, .apm/templates)
- Installation behavior (install.sh)
- User documentation (README.md)
Implement content changes in .apm/ first (never in repository .github/ as template source).
Update install.sh if source layout, copy logic, or install-time behavior changes.
Update README.md whenever behavior, structure, commands, or setup expectations change.
Validate and summarize what changed and why.

Mandatory Sync Rules

When any of the following happens, updates are required:

New file/folder added in .apm/:
- Update README.md structure or usage sections if users should know about it.
- Verify install.sh still copies it to client .github/.
File/folder renamed/moved in .apm/:
- Update install.sh assumptions if needed.
- Update all affected paths in README.md.
Install behavior changed:
- Update README.md Quick Install/Options/Manual Install sections.
Runtime expectations changed (for example, TECH initialization, force behavior, branch/tag behavior):
- Update both README.md and install.sh comments/output.

Do not leave behavior and docs out of sync.

Standards for New Files

Use clear, explicit naming aligned with SDP terms.
Keep templates generic and reusable across greenfield and legacy projects.
Prefer practical instructions over vague principles.
Preserve gate discipline and traceability across PRD -> backlog -> design -> plan -> implementation -> hardening.
Use ASCII by default.

Read the full file on GitHub · 78 lines

Changes

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.

3d ago First seen · 78 lines · 694 tokens per session scan A 86277bc731cd

Subscribe to this mod's changes

spec-development-protocol copilot-instructions.md is an instructions file published in the GitHub repository WojcikMM/spec-development-protocol (2 stars, last pushed 23d ago), licensed MIT. It adds 694 tokens to every session, about $0.0035 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Data and AI Planning

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).

microsoft/vscode · 6,785 tokens

spec-development-protocol copilot-instructions.md