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/cafgit 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.01472 | $0.01472 |
| Opus 5 | $0.00736 | $0.00736 |
| Sonnet 5 | $0.00294 | $0.00294 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade A, and why
plan-forge caf.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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Cloud Adoption Framework (CAF) Governance
Based on the Microsoft Cloud Adoption Framework for Azure. CAF is the environment governance layer — it governs how subscriptions, management groups, and shared services are organized across the enterprise, above the workload level.
Management Group Hierarchy
Root Management Group
├── Platform
│ ├── Identity (AAD, PIM, DNS)
│ ├── Management (Log Analytics, Automation, Backup)
│ └── Connectivity (hub VNet, ExpressRoute, Azure Firewall)
└── Landing Zones
├── Corp (internal workloads — connected to hub)
│ ├── Production subscriptions
│ └── Non-prod subscriptions
└── Online (internet-facing workloads — no hub connectivity required)
├── Production subscriptions
└── Non-prod subscriptions
IaC: Management Group Structure
// management-groups.bicep — deploy at tenant scope
targetScope = 'tenant'
resource landingZones 'Microsoft.Management/managementGroups@2023-04-01' = {
name: 'mg-landing-zones'
scope: tenant()
properties: {
displayName: 'Landing Zones'
details: { parent: { id: tenantResourceId('Microsoft.Management/managementGroups', rootMgId) } }
}
}
resource corpLz 'Microsoft.Management/managementGroups@2023-04-01' = {
name: 'mg-corp'
properties: {
displayName: 'Corp'
details: { parent: { id: landingZones.id } }
}
}
Subscription Design
| Pattern | When to Use |
|---|---|
| One subscription per workload | Default for most landing zones |
| One subscription per environment (dev/prod) | High-compliance or regulated workloads |
| Shared subscription | Only for non-production, shared infrastructure |
Subscription Naming
sub-{workload}-{environment}
sub-payments-prod
sub-payments-nonprod
sub-platform-identity
sub-platform-management
sub-platform-connectivity
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 · 200 lines · 1,472 tokens per session scan A 616a28f04662
plan-forge caf.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,472 tokens to every session, about $0.0074 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.