plan-forge: Instructions file for GitHub Copilot

.github/instructions/self-repair-reporting.instructions.md

plan-forge self-repair-reporting.instructions.md is an instructions file for GitHub Copilot from srnichols/plan-forge. It costs 1,327 tokens per session, scanned A, original, MIT.

Instructions for reporting defects in Plan Forge itself, the system used to create and run development plans. A meta-bug is a report about a problem in that system rather than in the project being built.

In plain words
What is it for?
Use it to decide when to file a self-repair report, choose the correct reporting tool, target repository, and labels after working around a Plan Forge defect.
Why use it?
It prevents bugs in Plan Forge's plans, command-line tool, orchestrator, or prompts from being mistaken for bugs in your own project.

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/self-repair-reporting.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 self-repair-reporting.instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/srnichols/plan-forge/self-repair-reporting"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/self-repair-reporting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,327 This file is loaded in full into every session.
When invoked 1,327 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.01327 $0.01327
Opus 5.5 $0.00531 $0.00531
Sonnet 5.5 $0.00265 $0.00265
Haiku 4.5 $0.00133 $0.00133

Measured 1mo ago against content hash 76cbc57d3934, 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 self-repair-reporting.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 1mo 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/self-repair-reporting.instructions.md · 127 lines

How it starts

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

Self-Repair Reporting

When to use: You discovered a defect in Plan Forge itself (plan files, orchestrator, CLI, prompts, instruction files) during execution and worked around it. File a meta-bug so the fix is captured.


Two Lanes at a Glance

Project Bug Meta Bug (Self-Repair)
What Bug in the code you're building Bug in Plan Forge itself
Tool forge_bug_file / tempering forge_meta_bug_file
Target repo Workspace git remote .forge.json#meta.selfRepairRepo → fallback srnichols/plan-forge
Labels bug, severity self-repair, class label

If the defect is in user project code, use forge_bug_file. If the defect is in Plan Forge's own plans, orchestrator, CLI, or prompts — use forge_meta_bug_file.


When to Fire forge_meta_bug_file

Fire the tool when you had to work around one of these three defect classes:

1. Plan Defect (plan-defect)

The plan file was wrong. Brittle validation gate, missing scope entry, wrong file path, over-narrow grep pattern, unsatisfiable dependency. You edited the plan or worked around the gate to keep moving.

2. Orchestrator / CLI Defect (orchestrator-defect)

Runtime bug in Plan Forge. Gate timeout too short, spawn failure on Windows, stash not popped after failed retry, estimator recommends a CLI-less model. You worked around it or the retry loop papered over it.

3. Prompt / Template Defect (prompt-defect)

A step-N prompt emitted unsafe output, an instruction file is missing a rule that would have prevented the problem, or a template placeholder wasn't expanded.


Worked Examples

Example 1: Brittle grep gate — plan-defect

Phase-28.2 Slice 2 — The plan gate used grep -q 'A' file || grep -q 'B' file but the worker chose identifier isApiOnlyModel, which matched neither pattern. The agent edited the plan gate inline to broaden the match.

{
  "class": "plan-defect",
  "title": "Phase-28.2 Slice 2 gate too narrow for chosen identifier",
  "symptom": "grep gate did not match worker's chosen export name",
  "workaround": "Edited plan gate to accept isApiOnlyModel",
  "slice": "2",
  "plan": "docs/plans/Phase-28.2-PLAN.md"
}

Read the full file on GitHub · 127 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. 1mo ago First seen · 127 lines · 1,327 tokens per session scan A 76cbc57d3934

Subscribe to this mod's changes

plan-forge self-repair-reporting.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed today), licensed MIT. It adds 1,327 tokens to every session, about $0.0053 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