plan-forge: Instructions file for GitHub Copilot

.github/instructions/architecture-principles.instructions.md

plan-forge architecture-principles.instructions.md is an instructions file for GitHub Copilot from srnichols/plan-forge. It costs 4,487 tokens per session, scanned A, original, MIT.

A set of instructions for planning software architecture before changing code. It emphasizes separating responsibilities, reusing existing patterns, using sound engineering practices, and considering TDD, which means writing tests around expected behavior during development.

In plain words
What is it for?
Use it as guidance before implementing features or fixes, especially when deciding where code belongs, how components should interact, and how business logic should be tested.
Why use it?
It helps prevent rushed fixes, duplicated code, missing types, and changes that work locally but do not fit the wider system.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is srnichols/plan-forge's own configuration. It tells GitHub Copilot how to work on plan-forge itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything plan-forge configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/srnichols/plan-forge/master/.github/instructions/architecture-principles.instructions.md
Clone the repo
git clone --depth 1 https://github.com/srnichols/plan-forge

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.

agentmods badge for plan-forge architecture-principles.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/srnichols/plan-forge/architecture-principles/github.svg)](https://agentmods.dev/instructions/srnichols/plan-forge/architecture-principles)
Your own site
<a href="https://agentmods.dev/instructions/srnichols/plan-forge/architecture-principles"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/architecture-principles/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.

agentmods 80×15 button for plan-forge architecture-principles.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/srnichols/plan-forge/architecture-principles"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/architecture-principles.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,487 This file is loaded in full into every session.
When invoked 4,487 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.04487 $0.04487
Opus 5.5 $0.01795 $0.01795
Sonnet 5.5 $0.00897 $0.00897
Haiku 4.5 $0.00449 $0.00449

Measured 11d ago against content hash 55bceda13e7d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan-forge architecture-principles.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 11d 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/instructions/architecture-principles.instructions.md · 321 lines

How it starts

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

Architecture-First Engineering Principles

Priority: CRITICAL — Read before ANY code changes Applies to: ALL files


AI Agent Instructions

┌─────────────────────────────────────────────────────────────────────────────┐
│  STOP! Before writing ANY code, you MUST:                                   │
│                                                                             │
│  1. ✅ Read this file (architecture-principles.instructions.md)             │
│  2. ✅ Follow the Decision Framework below                                  │
│  3. ✅ Apply Separation of Concerns                                         │
│  4. ✅ Consider TDD for business logic                                      │
│  5. ✅ Check existing patterns first (DON'T reinvent)                       │
│                                                                             │
│  🚨 RED FLAGS that MUST stop you:                                           │
│  ❌ "quick fix" → STOP, find proper solution                                │
│  ❌ "copy-paste" → STOP, create reusable abstraction                        │
│  ❌ "skip types" → STOP, add proper types                                   │
│  ❌ "we'll refactor later" → STOP, do it right now                          │
└─────────────────────────────────────────────────────────────────────────────┘

The 5 Questions Before Writing ANY Code

1. Does this code BELONG in this file/layer?

Layer Responsibility
Controllers / Routes HTTP handling only — no business logic
Services Business logic only — no data access
Repositories / Data Access Database queries only — no business rules
Components / Views UI rendering only — no side effects

2. Does a PATTERN already exist for this?

  • Search existing codebase for similar functionality
  • Check .github/instructions/*.instructions.md files
  • Follow existing patterns — don't create new approaches

3. Will this SCALE appropriately?

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

  1. 11d ago Changed · +18 lines · +615 tokens per session 55bceda13e7d
  2. 1mo ago First seen · 303 lines · 3,872 tokens per session scan A 6e436d950221

Subscribe to this mod's changes

plan-forge architecture-principles.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed today), licensed MIT. It adds 4,487 tokens to every session, about $0.0179 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.

Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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.

deepseek-ai/deepseek-harness · 4,261 tokens

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

microsoft/vscode · 2,731 tokens