Borrowing it
Nothing to install: this file belongs to srnichols/plan-forge. 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/srnichols/plan-forge/master/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/srnichols/plan-forge/copilot-instructions)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/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/srnichols/plan-forge/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/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.02696 | $0.02696 |
| Opus 5.5 | $0.01078 | $0.01078 |
| Sonnet 5.5 | $0.00539 | $0.00539 |
| Haiku 4.5 | $0.00270 | $0.00270 |
Grade A, and why
plan-forge 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 20d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions for Copilot
Project: Stack: Last Updated:
Architecture Principles
BEFORE making ANY code changes, read: .github/instructions/architecture-principles.instructions.md
Core Principles (Non-Negotiable)
- Architecture-First — Ask 5 questions before coding
- Separation of Concerns — Controller → Service → Repository
- Best Practices Over Speed — Enterprise-grade, not hacky
- TDD for Business Logic — Red-Green-Refactor
- Type Safety — Explicit types everywhere
Cost estimates
Cost estimates come from tools, not from chat math. When the user asks "how much will this plan cost?" or when you present any quorum-mode picker showing dollar amounts, you MUST call one of these tools first:
forge_estimate_quorum— projected cost of a plan under all four quorum modes (auto,power,speed,false) in one payload. Call this before showing any picker or decision matrix.forge_cost_report— actuals from previous runs (token counts, per-model spend, monthly aggregates).
Do not hand-compute quorum costs, do not invent dollar amounts in chat, and do not synthesize picker UIs without tool-backed numbers. Hand-computed quorum estimates have been observed to overshoot reality by an order of magnitude.
Talking to Forge-Master
For open-ended reasoning, use forge_master_ask instead of chaining
tools yourself. Forge-Master classifies your intent, fetches memory
context, and orchestrates read-only tool calls on your behalf.
- Use it for: multi-step reasoning about plans, troubleshooting failures, querying run status, funneling ideas into Crucible smelts.
- Don't use it for: direct file edits or code generation — Forge-Master is read-only.
- Example:
forge_master_ask({ message: "Why did Phase-27 Slice 4 fail?" })— Forge-Master callsforge_watch_live,brain_recall, andforge_bug_listto build an answer.
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.
- 20d ago Changed · +1 lines · +39 tokens per session c4dd37309a44
- 21d ago Changed · -13 tokens per session 79ab41ac1820
- 1mo ago First seen · 257 lines · 2,670 tokens per session scan A 624f88b84a33
plan-forge copilot-instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed today), licensed MIT. It adds 2,696 tokens to every session, about $0.0108 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
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).