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/versiongit 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.01404 | $0.01404 |
| Opus 5 | $0.00702 | $0.00702 |
| Sonnet 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 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 — 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.
- 2d 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 (5 stars, last pushed 21d ago), licensed MIT. It adds 1,404 tokens to every session, about $0.0070 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.
Perigon.CLI copilot-instructions.md
Instructions for AterDev/Perigon.CLI, covering github copilot instructions, general guidelines, 技术栈, 项目结构与分层 and 代码风格约定.
copilot-instructions copilot-instructions.md
Instructions for SebastienDegodez/copilot-instructions, covering copilot instructions, language policy, development code generation and workflow implementation.
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.