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.
npx agentmods add agents/srnichols/plan-forge/deploy-helpergit clone --depth 1 https://github.com/srnichols/plan-forgeWhat 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 | $0.00034 | $0.00874 |
| Opus 5 | $0.00017 | $0.00437 |
| Sonnet 5 | $0.00007 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00087 |
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.
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']"
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.
- 2d ago First seen · 122 lines · 34 tokens per session scan A ce7b0b53aa0d
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.
Other agents, from other repositories
observability
Learn how to use observability with Agent Framework.
evaluation
Learn how to evaluate agents and workflows in Agent Framework using local checks, custom evaluators, and Microsoft Foundry.
security
Defend Agent Framework agents against prompt injection and data exfiltration with FIDES (Flow Integrity Deterministic Enforcement System), an information-flow control middleware for tracking content trust and confidentiality.
structured-outputs
Learn how to use structured outputs with an agent.
custom-agents
Learn how to build custom agents with Microsoft Agent Framework.
running-agents
Learn how to run agents with Agent Framework.