What is autospec copilot-instructions.md?

Project instructions for AutoSpec, a framework that uses written specifications to guide software development. They require work to be tracked in a backlog and related documentation to stay current.

Use them when fixing bugs or building features in AutoSpec to update the backlog, maintain the appropriate documentation, and run the required quality checks.

They give changes a visible record and require verification before work is marked complete, reducing undocumented or unchecked changes.

How Hundia/autospec configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to Hundia/autospec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Hundia/autospec/main/.github/copilot-instructions.md

Clone the repo

git clone --depth 1 https://github.com/Hundia/autospec

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/hundia/autospec/copilot-instructions/github.svg)](https://agentmods.dev/instructions/hundia/autospec/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/hundia/autospec/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/hundia/autospec/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/hundia/autospec/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/hundia/autospec/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,388 This file is loaded in full into every session.

When invoked 1,388 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.01388	$0.01388
Opus 5.5	$0.00555	$0.00555
Sonnet 5.5	$0.00278	$0.00278
Haiku 4.5	$0.00139	$0.00139

Measured 2mo ago against content hash 48a74a495ebc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

autospec 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 2mo 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.

.github/copilot-instructions.md · 141 lines

How it starts

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

Copilot Instructions — AutoSpec

About This Project

AutoSpec is a Spec-Driven Development (SDD) framework. This project develops itself using its own tools. Use the prompt files in .github/prompts/ for sprint operations.

MANDATORY Development Workflow

Rule 1: Backlog-First Development

Every fix, feature, or change MUST be tracked in specs/backlog.md before or during implementation:

Determine if this is a bug (B.XX), new feature, or enhancement
Add ticket to specs/backlog.md in the appropriate sprint section
Set status to 🔄 In Progress when starting
Set status to ✅ Done when complete

Skip ONLY when user explicitly says "skip backlog", "don't track this"

Rule 2: Living Documentation

Every implemented feature MUST update docs/:

Viewer changes → docs/viewer/
CLI changes → docs/cli/
Methodology changes → docs/methodology/
Deployment changes → docs/deployment/
New subsystem → create new docs/<subsystem>/ directory

Rule 3: QA Before Done

No ticket is ✅ Done without verification:

Change Type	QA Required
Bug fix	Reproduce first, fix, verify user flow passes
CLI change	`npm run build` + `npm test` in `cli/`
Viewer change	`npm run build` in `viewer/` + visual check
Docs/config only	No QA — mark ✅ directly
New feature	Full test suite + new test cases if needed

Rule 4: Orchestrator + Agent Execution Pattern

This project uses the Orchestrator + Agent pattern for sprint execution:

Orchestrator writes agents/sprint-X-brief.md before spawning agents
Agent reads brief + relevant specs + docs, implements tickets
Agent updates: specs/backlog.md (🔲→✅), docs/, sprints/sprint-X/summary.md
Orchestrator reviews summary, spawns next sprint(s)

Project Structure

autospec/
├── .claude/commands/       # Claude Code skill files
├── .github/prompts/        # Copilot prompt files (YOU ARE HERE)
├── specs/                  # Role spec files (01-10) + backlog.md
├── agents/                 # Sprint briefing files (sprint-X-brief.md)
├── sprints/                # Sprint summaries (sprint-X/summary.md)
├── docs/                   # Living documentation
│   ├── methodology/        # SDD philosophy, roles, patterns
│   ├── viewer/             # Viewer app docs
│   ├── cli/                # CLI docs
│   └── deployment/         # CI/CD + GitHub Pages
├── skills/                 # Source skill files (claude/, copilot/, cursor/, etc.)
├── cli/                    # CLI tool source (Node/TypeScript)
├── viewer/                 # React viewer app
└── QUICKSTART.md           # Full usage guide

Read the full file on GitHub · 141 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.

2mo ago First seen · 141 lines · 1,388 tokens per session scan A 48a74a495ebc

Subscribe to this mod's changes

autospec copilot-instructions.md is an instructions file published in the GitHub repository Hundia/autospec (4 stars, last pushed 4mo ago), licensed MIT. It adds 1,388 tokens to every session, about $0.0056 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.

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 · 9,715 tokens

autospec: Instructions file for GitHub Copilot