Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/srnichols/plan-forge/release-checklistgit clone --depth 1 https://github.com/srnichols/plan-forgeWhat 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 | $0.02058 | $0.02058 |
| Opus 5 | $0.01029 | $0.01029 |
| Sonnet 5 | $0.00412 | $0.00412 |
| Haiku 4.5 | $0.00206 | $0.00206 |
Grade A, and why
plan-forge release-checklist.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 2d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Checklist auto-loader
You are editing a release-touching file. Before tagging, read docs/RELEASE-CHECKLIST.md end-to-end.
Why this file exists
Plan Forge has shipped broken releases multiple times because invariants weren't checked:
- v2.50.0/v2.51.0/v2.52.0 —
VERSIONshipped as-devinside the tarball - v2.76.0–v2.80.1 — tags pushed but no GitHub Release cut,
pforge self-updateinvisible to users for weeks - v2.59.x —
PreCommit.mjshook only mirrored to consuming projects after a downstream complaint - v2.82.0 —
postSlicehook +self-repair-reporting.instructions.mdmissing from setup/update enumerations
The canonical checklist lives at docs/RELEASE-CHECKLIST.md. Follow it for every tagged release.
Quick gates (verify before commit)
| Gate | Command | Pass criteria |
|---|---|---|
| Hooks mirrored | diff <(ls .github/hooks) <(ls templates/.github/hooks) |
Every file in .github/hooks/ also in templates/.github/hooks/ (plan-forge.json is templates-only) |
| Instruction enumeration | See §1b of checklist | Every .github/instructions/*.instructions.md is enumerated in setup.{ps1,sh} + pforge.{ps1,sh} (except project-principles which ships from templates/) |
| VERSION sync | git show vX.Y.Z:VERSION after tagging |
Exactly X.Y.Z, no -dev, no trailing newline |
| Release exists | node pforge-mcp/update-from-github.mjs resolve-tag |
{"ok":true,"tag":"vX.Y.Z"} with NO warning field |
| SDK default flipped | node --input-type=module -e "import{loadCopilotSdkPreference}from'./pforge-mcp/orchestrator/worker-spawn.mjs';import os from'node:os';const v=loadCopilotSdkPreference(os.tmpdir());if(v!=='prefer')throw new Error('default not flipped, got: '+v)" |
Exits 0 — confirms routing.copilotSdk defaults to 'prefer' with no .forge.json present |
| No stale "off by default" in CHANGELOG | node -e 'const s=require("fs").readFileSync("CHANGELOG.md","utf8");const u=s.slice(0,s.indexOf("## [3.25.1]"));if(u.includes("off by default"))throw new Error("CHANGELOG still claims the SDK route is off by default")' |
Exits 0 — the unreleased block must not contain the phrase off by default |
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.
- 2d ago First seen · 92 lines · 2,058 tokens per session scan A 01099c6d1300
plan-forge release-checklist.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 22d ago), licensed MIT. It adds 2,058 tokens to every session, about $0.0103 per session on Opus 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
dotnet-skills AGENTS.md
Instructions for managedcode/dotnet-skills, covering agents.md, purpose, solution topology, rule precedence and path and linking rules.
dotnet-skills copilot-instructions.md
Instructions for managedcode/dotnet-skills: Use AGENTS.md as the repository-wide source of truth for workflow, catalog structure, release policy, and skill maintenance rules.
copilot-instructions copilot-instructions.md
Instructions for SebastienDegodez/copilot-instructions, covering copilot instructions, language policy, development code generation and workflow implementation.
Perigon.CLI copilot-instructions.md
Instructions for AterDev/Perigon.CLI, covering github copilot instructions, general guidelines, 技术栈, 项目结构与分层 and 代码风格约定.
maf-doctor maf-deployment.instructions.md
Always-loaded production-deployment patterns for MAF 1.3.0. Auto-applies to Program.cs, DI registration files, and infra config. Covers ManagedIdentityCredential, MaxTokens caps, secret handling, OpenTelemetry wiring, and the analyzer rules that catch regressions at write time.
maf-doctor copilot-instructions.md
Instructions for joslat/maf-doctor, covering maf 1.3.0 migration — auto-loaded constraints, maf 1.3.0 — constraints & breaking changes reference, hard constraints (never violate), fan-out / fan-in rules (silent failure risk) and key breaking changes.