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/waf)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/waf"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/waf/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/waf"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/waf.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.01489 | $0.01489 |
| Opus 5.5 | $0.00596 | $0.00596 |
| Sonnet 5.5 | $0.00298 | $0.00298 |
| Haiku 4.5 | $0.00149 | $0.00149 |
Grade A, and why
plan-forge waf.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 21d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Well-Architected Framework (WAF)
Based on the Microsoft Azure Well-Architected Framework. The WAF is the workload quality layer — it governs individual service design decisions.
The 5 Pillars
| Pillar | Core Question |
|---|---|
| Reliability | Will it stay available when things go wrong? |
| Security | Is the workload protected end-to-end? |
| Cost Optimization | Are we paying for what we actually use? |
| Operational Excellence | Can we deploy, operate, and recover safely? |
| Performance Efficiency | Does it scale and respond well under load? |
Reliability
Key Controls
// ✅ Deploy across availability zones — never single-zone in production
resource appServicePlan 'Microsoft.Web/serverfarms@2025-03-01' = {
sku: { name: 'P1v3', tier: 'PremiumV3', capacity: 2 }
properties: {
zoneRedundant: true // ← required for zone-pinned AZ support
}
}
// ✅ Health probes on load balancers and App Gateway
// ✅ Auto-scale rules based on CPU + memory, not just time-based
// ✅ Azure backup enabled for databases and storage
// ✅ Soft-delete + point-in-time restore for all databases
Reliability Checklist
- Resources deployed across ≥ 2 availability zones in production
- Auto-scale configured with appropriate min/max and cool-down
- Health checks / probes on every outward-facing service
- Recovery Time Objective (RTO) and Recovery Point Objective (RPO) defined
- Azure Backup enabled for databases and critical storage
- Geo-redundant storage (GRS or RA-GRS) for critical data in production
- Azure Site Recovery evaluated for VM/stateful workloads
- Circuit breaker / retry policies in application code (not just infra)
Security
See
security.instructions.mdfor the detailed Azure IaC security patterns.
WAF Security Checklist
- Managed Identity for all service-to-service auth — no static credentials
- Key Vault for all secrets, certificates, and keys
- Private endpoints for all PaaS services in production
- Azure DDoS Protection Standard on public-facing VNets
- Azure Web Application Firewall (WAF) on Application Gateway or Front Door
- Defender for Cloud Standard tier enabled on all subscriptions
- Just-in-time (JIT) VM access enabled
- Azure AD Conditional Access policies configured
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.
- 21d ago Changed 16b483a443eb
- 1mo ago First seen · 176 lines · 1,489 tokens per session scan A a550d9a31ee2
plan-forge waf.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed yesterday), licensed MIT. It adds 1,489 tokens to every session, about $0.0060 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
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).