plan-forge deploy.instructions.md

A set of instructions for building Azure infrastructure deployment pipelines with GitHub Actions or Azure DevOps, using OIDC for sign-in.

In plain words
What is it for?
Use it to set up validation and deployment stages for Azure Infrastructure as Code, including federated authentication and rollback guidance.
Why use it?
It provides a repeatable deployment pattern that avoids storing long-lived cloud client secrets in the pipeline.

Instructions file for GitHub Copilot

Install

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.

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

Made for: GitHub Copilot.

Per session 1,667 This file is loaded in full into every session.
When invoked 1,667 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.01667 $0.01667
Opus 5 $0.00834 $0.00834
Sonnet 5 $0.00333 $0.00333
Haiku 4.5 $0.00167 $0.00167

Measured yesterday against content hash 47f7a53e35a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan-forge deploy.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 yesterday.

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/deploy.instructions.md · 238 lines

How it starts

The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Azure IaC Pipeline Patterns

Authentication — Workload Identity Federation (OIDC)

Use OIDC/Workload Identity Federation everywhere — no stored client secrets.

GitHub Actions Setup

# One-time setup: configure the federated credential
azd pipeline config   # automatically configures OIDC for GitHub Actions

Required secrets in GitHub:

  • AZURE_CLIENT_ID — App Registration client ID
  • AZURE_TENANT_ID — Azure AD tenant ID
  • AZURE_SUBSCRIPTION_ID — target subscription

Azure DevOps Setup

Use a service connection with Workload Identity Federation:

Project Settings → Service connections → New → Azure Resource Manager → Workload Identity Federation

GitHub Actions — Bicep Deployment Pipeline

# .github/workflows/infra-deploy.yml
name: Infrastructure Deploy

on:
  push:
    branches: [main]
    paths: ['infra/**']
  pull_request:
    branches: [main]
    paths: ['infra/**']
  workflow_dispatch:

permissions:
  id-token: write      # required for OIDC
  contents: read

jobs:
  validate:
    name: Validate
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Azure Login (OIDC)
        uses: azure/login@v2
        with:
          client-id: ${{ secrets.AZURE_CLIENT_ID }}
          tenant-id: ${{ secrets.AZURE_TENANT_ID }}
          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}

      - name: Install Bicep CLI
        run: az bicep install

      - name: Lint Bicep
        run: az bicep lint --file infra/main.bicep

      - name: Bicep Build (validate ARM output)
        run: az bicep build --file infra/main.bicep

      - name: What-If Analysis
        run: |
          az deployment group what-if \
            --resource-group ${{ vars.RESOURCE_GROUP }} \
            --template-file infra/main.bicep \
            --parameters infra/main.parameters.json \
            --no-pretty-print

  deploy-dev:
    name: Deploy Dev
    needs: validate
    runs-on: ubuntu-latest
    environment: dev
    if: github.ref == 'refs/heads/main'
    steps:
      - uses: actions/checkout@v4
      - uses: azure/login@v2
        with:
          client-id: ${{ secrets.AZURE_CLIENT_ID }}
          tenant-id: ${{ secrets.AZURE_TENANT_ID }}
          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}

      - name: Deploy Bicep
        uses: azure/arm-deploy@v2
        with:
          resourceGroupName: ${{ vars.DEV_RESOURCE_GROUP }}
          template: infra/main.bicep
          parameters: infra/main.parameters.json environmentName=dev
          failOnStdErr: true

      - name: Smoke Test
        shell: pwsh
        run: ./scripts/Invoke-SmokeTest.ps1 -EnvironmentName dev

  deploy-prod:
    name: Deploy Production
    needs: deploy-dev
    runs-on: ubuntu-latest
    environment: prod           # requires manual approval gate in GitHub
    steps:
      - uses: actions/checkout@v4
      - uses: azure/login@v2
        with:
          client-id: ${{ secrets.AZURE_CLIENT_ID }}
          tenant-id: ${{ secrets.AZURE_TENANT_ID }}
          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}

      - name: Deploy Bicep
        uses: azure/arm-deploy@v2
        with:
          resourceGroupName: ${{ vars.PROD_RESOURCE_GROUP }}
          template: infra/main.bicep
          parameters: infra/main.parameters.json environmentName=prod
          failOnStdErr: true

Read the full file on GitHub · 238 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. yesterday First seen · 238 lines · 1,667 tokens per session scan A 47f7a53e35a2

Subscribe to this mod's changes

plan-forge deploy.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 21d ago), licensed MIT. It adds 1,667 tokens to every session, about $0.0083 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.

Related

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.

managedcode/dotnet-skills · 13,592 tokens

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.

managedcode/dotnet-skills · 97 tokens

Perigon.CLI copilot-instructions.md

Instructions for AterDev/Perigon.CLI, covering github copilot instructions, general guidelines, 技术栈, 项目结构与分层 and 代码风格约定.

AterDev/Perigon.CLI · 1,254 tokens

copilot-instructions copilot-instructions.md

Instructions for SebastienDegodez/copilot-instructions, covering copilot instructions, language policy, development code generation and workflow implementation.

SebastienDegodez/copilot-instructions · 364 tokens

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.

joslat/maf-doctor · 1,884 tokens

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.

joslat/maf-doctor · 1,604 tokens