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/naminggit 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.01453 | $0.01453 |
| Opus 5 | $0.00727 | $0.00727 |
| Sonnet 5 | $0.00291 | $0.00291 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
plan-forge naming.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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Naming Conventions
Based on the Microsoft Cloud Adoption Framework (CAF) naming convention.
Pattern
{type}-{workload}-{environment}-{region}-{instance}
| Segment | Example | Notes |
|---|---|---|
type |
rg, vnet, app |
See abbreviation table below |
workload |
payments, auth |
Short, meaningful, no spaces |
environment |
dev, test, staging, prod |
Abbreviated if character-limited |
region |
eastus, eus, we |
Use short form when constrained |
instance |
001, 002 |
Zero-padded; use only when multiple instances exist |
Resource Abbreviations (CAF)
| Resource Type | Abbreviation | Example |
|---|---|---|
| Resource group | rg |
rg-payments-prod-eastus |
| Virtual network | vnet |
vnet-payments-prod-eastus |
| Subnet | snet |
snet-app-prod-eastus |
| Network security group | nsg |
nsg-app-prod-eastus |
| App Service plan | asp |
asp-payments-prod-eastus |
| App Service / Web app | app |
app-payments-prod-eastus |
| Function app | func |
func-payments-prod-eastus |
| Container app | ca |
ca-payments-prod-eastus |
| Container App Environment | cae |
cae-payments-prod-eastus |
| SQL server | sql |
sql-payments-prod-eastus |
| SQL database | sqldb |
sqldb-payments-prod-eastus |
| Cosmos DB account | cosmos |
cosmos-payments-prod-eastus |
| Storage account | st |
stpaymentsprod001 ← no dashes, max 24 chars |
| Key vault | kv |
kv-payments-prod-eus-001 ← max 24 chars |
| Log Analytics workspace | log |
log-payments-prod-eastus |
| Application Insights | appi |
appi-payments-prod-eastus |
| User-assigned managed identity | id |
id-payments-prod-eastus |
| Service Bus namespace | sb |
sb-payments-prod-eastus |
| Event Hub namespace | evhns |
evhns-payments-prod-eastus |
| Container registry | cr |
crpaymentsprod001 ← no dashes, alphanumeric only |
| AKS cluster | aks |
aks-payments-prod-eastus |
| API Management | apim |
apim-payments-prod-eastus |
| Front Door | afd |
afd-payments-prod-eastus |
| Virtual machine | vm |
vmpaymentspd001 ← max 15 chars Windows / 64 Linux |
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 · 125 lines · 1,453 tokens per session scan A c91e1189c8f1
plan-forge naming.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 22d ago), licensed MIT. It adds 1,453 tokens to every session, about $0.0073 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
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.
dotnet-skills AGENTS.md
Instructions for managedcode/dotnet-skills, covering agents.md, purpose, solution topology, rule precedence and path and linking rules.
optio CLAUDE.md
Instructions for jonwiggins/optio, covering claude.md, what is optio?, architecture, pod-per-repo with worktrees and worktree lifecycle.
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.
apex-accelerator copilot-instructions.md
Instructions for jonathan-vella/apex-accelerator, covering apex - copilot instructions, azure defaults (canonical), default regions, required tags (azure policy enforced) and security baseline + avm mandate.
apex-accelerator iac-terraform-best-practices.instructions.md
Terraform-specific IaC best practices for Azure templates. AVM-first, CAF naming, security baseline, provider pins.