Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/srnichols/plan-forgenpx agentmods add instructions/srnichols/plan-forge/azdWrote 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/azd)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/azd"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/azd/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/azd"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/azd.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.01500 | $0.01500 |
| Opus 5.5 | $0.00600 | $0.00600 |
| Sonnet 5.5 | $0.00300 | $0.00300 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade A, and why
plan-forge azd.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 19d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Developer CLI (azd) Best Practices
Required Structure
Every azd-compatible project requires:
project-root/
├── azure.yaml ← service definition (required)
├── infra/ ← IaC files (default; change with infra.path)
│ ├── main.bicep ← or main.tf for Terraform
│ ├── main.parameters.json
│ └── modules/
├── .azure/ ← azd environment state (git-ignored)
└── src/ ← application source code (optional for pure infra)
azure.yaml
# azure.yaml — maps app services to provisioned Azure resources
name: myapp # must match infra resource naming
metadata:
template: [email protected] # optional: template origin tracking
# Infrastructure provider (default: bicep)
infra:
provider: bicep # bicep | terraform
path: infra # relative path to IaC files (default: infra)
module: main # root module filename without extension (default: main)
services:
api:
project: ./src/api # relative path to service source
language: dotnet # dotnet | js | ts | python | java
host: containerapp # appservice | containerapp | function | staticwebapp | aks
docker:
path: ./src/api/Dockerfile
context: ./src/api
web:
project: ./src/web
language: js
host: staticwebapp
dist: build # relative path to built artifacts
# Pipeline provider (default: github)
pipeline:
provider: github # github | azdo
Terraform Variant
name: myapp-terraform
infra:
provider: terraform
path: infra
services:
api:
project: ./src/api
language: dotnet
host: containerapp
Required Resource Tags for azd Auto-Discovery
When resourceName is NOT set in azure.yaml, azd discovers resources by tags:
// In your Bicep module — tag resources so azd can find them
resource containerApp 'Microsoft.App/containerApps@2026-01-01' = {
tags: union(commonTags, {
'azd-env-name': environmentName // ← required for azd discovery
'azd-service-name': 'api' // ← must match service key in azure.yaml
})
}
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.
- 19d ago Changed · +1 tokens per session e00d252da9fd
- 1mo ago First seen · 215 lines · 1,499 tokens per session scan A 3b0cdf5446a8
plan-forge azd.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed 7d ago), licensed MIT. It adds 1,500 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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.