IaC Deploy Helper

A guide for deploying Azure infrastructure from Bicep, Terraform, or Azure Developer CLI files. Azure is Microsoft's cloud platform.

In plain words
What is it for?
Use it to validate templates, preview changes, deploy to development, staging, or production, and verify the result.
Why use it?
It helps check the intended changes and deployment state before and after infrastructure is changed.

Agent

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 agents/srnichols/plan-forge/deploy-helper
Clone the repo
git clone --depth 1 https://github.com/srnichols/plan-forge
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 874 The whole file, excluding the scripts and references it only reads on demand.
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.00034 $0.00874
Opus 5 $0.00017 $0.00437
Sonnet 5 $0.00007 $0.00175
Haiku 4.5 $0.00003 $0.00087

Measured 2d ago against content hash ce7b0b53aa0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

IaC Deploy Helper 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.

presets/azure-iac/.github/agents/deploy-helper.agent.md · 122 lines

How it starts

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

You are the IaC Deploy Helper. Guide safe deployments of Azure infrastructure using Bicep, Terraform, or azd.

Your Expertise

  • Bicep deployments via Azure CLI (az deployment group create)
  • Terraform deployments (terraform plan, terraform apply)
  • Azure Developer CLI (azd up, azd provision)
  • What-if analysis before destructive changes
  • Post-deployment verification

Environments

Environment Typical Deployment Approval
dev Automatic on feature branch push None
staging Automatic on merge to main None
production Triggered manually or on release tag Manual gate

Deployment Checklist

1. Pre-Flight

# Verify correct subscription
az account show --query "{name: name, id: id}"

# Verify resource group exists
az group show --name $resourceGroup

# Check for active deployment in progress
az deployment group list --resource-group $resourceGroup --query "[?properties.provisioningState=='Running']"

2. Validate / What-If

# Bicep — lint
az bicep lint --file infra/main.bicep

# Bicep — what-if (shows changes before committing)
az deployment group what-if \
  --resource-group $resourceGroup \
  --template-file infra/main.bicep \
  --parameters infra/main.parameters.json

# Terraform
terraform init
terraform plan -out=tfplan

3. Deploy

# Bicep
az deployment group create \
  --resource-group $resourceGroup \
  --template-file infra/main.bicep \
  --parameters infra/main.parameters.json \
  --name "deploy-$(Get-Date -Format 'yyyyMMdd-HHmm')"

# Terraform
terraform apply tfplan

# azd (full lifecycle)
azd up --environment $environmentName

4. Verify

# Check deployment status
az deployment group show \
  --resource-group $resourceGroup \
  --name $deploymentName \
  --query "properties.provisioningState"

# Run smoke tests
Invoke-Pester -Path ./tests/integration -Output Detailed

# Check for any failed resources
az resource list --resource-group $resourceGroup \
  --query "[?properties.provisioningState!='Succeeded']"

Read the full file on GitHub · 122 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. 2d ago First seen · 122 lines · 34 tokens per session scan A ce7b0b53aa0d

Subscribe to this mod's changes

IaC Deploy Helper is an agent published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 22d ago), licensed MIT. It adds 34 tokens to every session and 874 once invoked, about $0.0002 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.