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.
git 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/version)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/version"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/version/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/version"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/version.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.01404 | $0.01404 |
| Opus 5.5 | $0.00562 | $0.00562 |
| Sonnet 5.5 | $0.00281 | $0.00281 |
| Haiku 4.5 | $0.00140 | $0.00140 |
Grade A, and why
plan-forge version.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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Management (.NET)
Versioning Scheme
MAJOR.MINOR.PATCH.BUILD
3 . 7 . 2 . 142
| Segment | When to Increment | Trigger |
|---|---|---|
| MAJOR | Breaking API changes | Manual approval required |
| MINOR | New features (backward-compatible) | feat: commit prefix |
| PATCH | Bug fixes, performance, refactors | fix: / perf: / refactor: prefix |
| BUILD | Every build (auto-increment) | docs: / chore: / test: / ci: / style: |
Commit Message → Version Bump
| Commit Prefix | Version Impact | Example |
|---|---|---|
feat: |
MINOR +1 | 3.6.0.0 → 3.7.0.0 |
fix: / perf: / refactor: |
PATCH +1 | 3.6.5.0 → 3.6.6.0 |
docs: / chore: / test: / style: / ci: |
BUILD +1 | 3.6.5.418 → 3.6.5.419 |
feat!: / BREAKING CHANGE: |
Requires manual MAJOR bump | Approval workflow |
Implementation with Directory.Build.props
<Project>
<PropertyGroup>
<VersionPrefix>3.7.2</VersionPrefix>
<VersionSuffix></VersionSuffix>
<!-- BUILD number auto-incremented by CI or build script -->
<FileVersion>$(VersionPrefix).$(BuildNumber)</FileVersion>
<InformationalVersion>$(VersionPrefix)+$(GitCommitHash)</InformationalVersion>
</PropertyGroup>
</Project>
Version Endpoint
Expose version info at runtime:
app.MapGet("/api/version", () => new
{
Version = typeof(Program).Assembly.GetName().Version?.ToString(),
Informational = typeof(Program).Assembly
.GetCustomAttribute<AssemblyInformationalVersionAttribute>()?.InformationalVersion,
Environment = app.Environment.EnvironmentName
});
Rules
- NEVER manually edit version numbers in
.csproj— use build scripts - ALWAYS use conventional commit prefixes to drive version bumps
- ALWAYS tag releases:
git tag v3.7.0after MINOR/MAJOR bumps - MAJOR bumps require explicit approval — never automatic
- CI pipeline reads commit messages and calls appropriate bump script
InformationalVersionshould include Git SHA for traceability
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 a808ff8152cc
- 1mo ago First seen · 169 lines · 1,404 tokens per session scan A f4f7881064c0
plan-forge version.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed 8d ago), licensed MIT. It adds 1,404 tokens to every session, about $0.0056 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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.