Borrowing it
Nothing to install: this file belongs to girishr/SpecPilot. 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/girishr/SpecPilot/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/girishr/SpecPilotWrote 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/girishr/specpilot/copilot-instructions)<a href="https://agentmods.dev/instructions/girishr/specpilot/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/girishr/specpilot/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/girishr/specpilot/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/girishr/specpilot/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.00868 | $0.00868 |
| Opus 5.5 | $0.00347 | $0.00347 |
| Sonnet 5.5 | $0.00174 | $0.00174 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
SpecPilot 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 16d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Coding Instructions — SpecPilot
This file is automatically read by GitHub Copilot, Cursor, and other AI tools on every request. Keep this file short — only critical mandates. Full context is in
.specs/project/project.yaml.
Project
- Name: SpecPilot
- Stack: TypeScript / Node.js / Commander.js
- Specs location:
.specs/
🔴 Critical Mandates — Never violate, no exceptions
- NEVER commit code to git unless the developer explicitly asks. Always ask first.
- NEVER push to git unless the developer explicitly asks. Always ask first.
- NEVER deploy, publish, or release the project unless the developer explicitly asks. Always ask first.
- NEVER modify the
.specs/folder structure, subfolder names, or file names. Only update file contents. - ALWAYS update affected
.specs/files after every code change — without being asked:- Structural changes →
architecture/architecture.md - Feature changes →
project/requirements.md - Test changes →
quality/tests.md - Task status →
planning/tasks.md - Completed work →
CHANGELOG.md
- Structural changes →
- NEVER describe, quote, or reference file contents without first reading the file via a tool call in this session. If you have not read the file yet, say so explicitly before answering.
- NEVER implement, write code, or make file changes unless the developer explicitly asks. If the next step seems obvious, ask first — do not assume.
- SPEC-FIRST review gate: Before touching any code or non-spec files, read all relevant
.specs/files, update all affected spec files first, present a Spec Report summarizing what changed, which files were affected, and what the specs now say, then wait for the developer's explicityes, proceedbefore writing code. If the developer declines, revert the spec changes and stop.
🟡 Process Mandates
- Spec-First: Update
.specs/before writing code. - Log all AI interactions in
.specs/development/prompts.mdwith timestamps. - Document decisions in
.specs/development/context.md. - Tasks: When the SpecPilot MCP tools are connected, use them to add and move tasks. Otherwise edit
.specs/planning/tasks.mddirectly and keep its table format.
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.
- 16d ago Changed · +1 lines · +38 tokens per session 78b18a8f1a0d
- 2mo ago First seen · 69 lines · 830 tokens per session scan A 2dc4cf321e6d
SpecPilot copilot-instructions.md is an instructions file published in the GitHub repository girishr/SpecPilot (39 stars, last pushed today), licensed MIT. It adds 868 tokens to every session, about $0.0035 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
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.