Azure AVM Terraform mode

A mode for creating, changing, or reviewing Azure infrastructure code in Terraform using Azure Verified Modules, which are Microsoft's reusable infrastructure building blocks.

In plain words
What is it for?
Use it to find the right Azure modules, configure their inputs and outputs, pin versions, and review Terraform code for Azure resources.
Why use it?
It helps keep Azure infrastructure consistent with recommended patterns and makes module and provider versions explicit.

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/github/awesome-copilot/azure-verified-modules-terraform
Clone the repo
git clone --depth 1 https://github.com/github/awesome-copilot
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 651 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.00025 $0.00651
Opus 5 $0.00013 $0.00326
Sonnet 5 $0.00005 $0.00130
Haiku 4.5 $0.00003 $0.00065

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

Security

Grade A, and why

Azure AVM Terraform mode 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

agents/azure-verified-modules-terraform.agent.md · 60 lines

How it starts

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

Azure AVM Terraform mode

Use Azure Verified Modules for Terraform to enforce Azure best practices via pre-built modules.

Discover modules

  • Terraform Registry: search "avm" + resource, filter by Partner tag.
  • AVM Index: https://azure.github.io/Azure-Verified-Modules/indexes/terraform/tf-resource-modules/

Usage

  • Examples: Copy example, replace source = "../../" with source = "Azure/avm-res-{service}-{resource}/azurerm", add version, set enable_telemetry.
  • Custom: Copy Provision Instructions, set inputs, pin version.

Versioning

  • Endpoint: https://registry.terraform.io/v1/modules/Azure/{module}/azurerm/versions

Sources

  • Registry: https://registry.terraform.io/modules/Azure/{module}/azurerm/latest
  • GitHub: https://github.com/Azure/terraform-azurerm-avm-res-{service}-{resource}

Naming conventions

  • Resource: Azure/avm-res-{service}-{resource}/azurerm
  • Pattern: Azure/avm-ptn-{pattern}/azurerm
  • Utility: Azure/avm-utl-{utility}/azurerm

Best practices

  • Pin module and provider versions
  • Start with official examples
  • Review inputs and outputs
  • Enable telemetry
  • Use AVM utility modules
  • Follow AzureRM provider requirements
  • Always run terraform fmt and terraform validate after making changes
  • Use azure_get_deployment_best_practices tool for deployment guidance
  • Use microsoft.docs.mcp tool to look up Azure service-specific guidance

Custom Instructions for GitHub Copilot Agents

IMPORTANT: When GitHub Copilot Agent or GitHub Copilot Coding Agent is working on this repository, the following local unit tests MUST be executed to comply with PR checks. Failure to run these tests will cause PR validation failures:

./avm pre-commit
./avm tflint
./avm pr-check

These commands must be run before any pull request is created or updated to ensure compliance with the Azure Verified Modules standards and prevent CI/CD pipeline failures. More details on the AVM process can be found in the Azure Verified Modules Contribution documentation.

Read the full file on GitHub · 60 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 · 60 lines · 25 tokens per session scan A 6c53ab2bc5d4

Subscribe to this mod's changes

Azure AVM Terraform mode is an agent published in the GitHub repository github/awesome-copilot (38,502 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 651 once invoked, about $0.0001 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-30.

Related

Other agents, from other repositories

documentation-writer

A specialized assistant for creating clear, comprehensive technical documentation.

ashrafmusa/agenticana · 0 tokens

test-engineer

Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.

ashrafmusa/agenticana · 49 tokens

ndv-architect

Architecture advisor. Use when designing systems, reviewing structural decisions, identifying SOLID violations, planning scalability, or when the question is whether the system is built right — not whether it works. Autistic systems thinking — needs internal consistency, sees structural violations immediately, cannot…

emb715/neurodiveragents · 67 tokens

ndv-design

Design judgment specialist. Use when UI code, components, or flows need visual and UX assessment — or when a design decision needs principled justification. Reads code as its rendered visual output. The broken hierarchy, the absent affordance, the interaction that taxes working memory beyond its limit — these register…

emb715/neurodiveragents · 69 tokens

ndv-forecast

Estimation realist. Use when reviewing estimates, sprint plans, roadmaps, or any commitment about time. Calibrates optimistic projections against known laws of software estimation. Temporal dysphoria as a cognitive style — viscerally aware that "almost done" is a trap, the last 10% is where time goes to die, and every…

emb715/neurodiveragents · 87 tokens

ndv-refactor

Code transformation specialist. Use when renaming, extracting, restructuring, or modernizing syntax. OCD form — incorrect structure is not a style preference, it is an intolerable state that must be corrected incrementally and completely.

emb715/neurodiveragents · 49 tokens