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/instructions/release-checklist.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/release-checklist)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/release-checklist"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/release-checklist/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/release-checklist"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/release-checklist.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.02115 | $0.02115 |
| Opus 5.5 | $0.00846 | $0.00846 |
| Sonnet 5.5 | $0.00423 | $0.00423 |
| Haiku 4.5 | $0.00212 | $0.00212 |
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 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 — 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. node scripts/release/ship.mjs --version X.Y.Z --title "…" --worktree <master worktree> runs §3 end to end (dry run unless --execute; resume with --from-step).
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 routing contract | 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('unexpected SDK default: '+v)" |
The default has been "prefer" since v3.29 (#307 cost-parity evidence). Use a temporary directory with no config for the check. Changing it again requires new benchmark evidence, not an automatic release-time edit. |
| SDK migration notes | Compare the candidate's routing default and Node floor with the preceding release | Only a release changing either contract needs the corresponding migration notes and cost-parity/default-flip gates below. Do not apply the old Phase-60 default-flip gate to an unrelated patch release. |
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 · +48 tokens per session 2f6f254a66e3
- 21d ago Changed · +36 tokens per session ed7bcf714d49
- 1mo ago Changed · -27 tokens per session 1e429cb0c14b
- 1mo 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 (6 stars, last pushed today), licensed MIT. It adds 2,115 tokens to every session, about $0.0085 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).