plan-forge azd.instructions.md

plan-forge azd.instructions.md is an instructions file for GitHub Copilot from srnichols/plan-forge. It costs 1,500 tokens per session, scanned A, original, MIT.

A set of written rules for projects using Azure Developer CLI, Microsoft's command-line tool for deploying applications to Azure.

In plain words
What is it for?
It guides the structure of azure.yaml, infrastructure files, services, environment state, tags, hooks, and pipelines.
Why use it?
It gives the coding agent a consistent project layout and configuration pattern, reducing confusion about where deployment settings and infrastructure belong.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is project: ./src/api # relative path to service source.

Good fit It guides the structure of azure.yaml, infrastructure files, services, environment state, tags, hooks, and pipelines.

Compare 6 instructions from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/srnichols/plan-forge
agentmods
npx agentmods add instructions/srnichols/plan-forge/azd

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for plan-forge azd.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/srnichols/plan-forge/azd/github.svg)](https://agentmods.dev/instructions/srnichols/plan-forge/azd)
Your own site
<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.

agentmods 80×15 button for plan-forge azd.instructions.md

Your own site · 80×15
<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>
Per session 1,500 This file is loaded in full into every session.
When invoked 1,500 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. ✓ AI security review Fable 5.1 · 6 Sept 2026 📄 Read the review
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 19d ago against content hash e00d252da9fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

presets/azure-iac/.github/instructions/azd.instructions.md · 215 lines

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
  })
}

Read the full file on GitHub · 215 lines

Changes

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.

  1. 19d ago Changed · +1 tokens per session e00d252da9fd
  2. 1mo ago First seen · 215 lines · 1,499 tokens per session scan A 3b0cdf5446a8

Subscribe to this mod's changes

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.

Related

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).

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,384 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

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.

denoland/deno · 3,077 tokens