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/policygit 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.02019 | $0.02019 |
| Opus 5 | $0.01009 | $0.01009 |
| Sonnet 5 | $0.00404 | $0.00404 |
| Haiku 4.5 | $0.00202 | $0.00202 |
Grade A, and why
plan-forge policy.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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Policy & Initiative Compliance
Azure Policy is the enforcement layer — it makes Landing Zone standards compulsory, not optional.
Policy Effect Hierarchy
| Effect | Behavior | Typical Use |
|---|---|---|
Disabled |
Policy off | Temporary suppression only |
Audit |
Log non-compliance; allow resource | Discovery, initial rollout |
AuditIfNotExists |
Audit if related resource is missing | Check for associated resources |
Modify |
Auto-correct tags or properties | Tag enforcement |
Append |
Add properties without replace | Adding tags |
DeployIfNotExists |
Auto-deploy missing resources | Diagnostic settings, agents |
Deny |
Block non-compliant resource creation | Enforce hard requirements |
Progressive rollout: Start with
Audit, validate coverage, then promote toDeny.
Core Policy Assignments (Landing Zone Level)
// Assignment at management group scope — applies to all child subscriptions
targetScope = 'managementGroup'
// ✅ Deploy diagnostic settings automatically (DeployIfNotExists)
resource diagPolicy 'Microsoft.Authorization/policyAssignments@2023-04-01' = {
name: 'deploy-diagnostic-settings'
location: 'eastus'
identity: { type: 'SystemAssigned' } // ← DINE policies require managed identity
properties: {
policyDefinitionId: '/providers/Microsoft.Authorization/policySetDefinitions/{initiative-id}'
enforcementMode: 'Default'
parameters: {
logAnalyticsWorkspaceId: { value: logAnalyticsWorkspaceId }
}
}
}
// ✅ Deny public network access on storage accounts
resource denyPublicStorage 'Microsoft.Authorization/policyAssignments@2023-04-01' = {
name: 'deny-public-storage'
properties: {
policyDefinitionId: '/providers/Microsoft.Authorization/policyDefinitions/b2982f36-99f2-4db5-8eff-19bf0ddc60be'
enforcementMode: 'Default'
displayName: 'Deny public network access on Storage Accounts'
}
}
// ✅ Require mandatory tags (Deny effect)
resource requireTagsPolicy 'Microsoft.Authorization/policyAssignments@2023-04-01' = {
name: 'require-mandatory-tags'
properties: {
policyDefinitionId: mandatoryTagsInitiativeId
enforcementMode: 'Default'
}
}
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 · 244 lines · 2,019 tokens per session scan A 9234e236bfc9
plan-forge policy.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 22d ago), licensed MIT. It adds 2,019 tokens to every session, about $0.0101 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.