Azure AVM Bicep mode

A guide for creating and reviewing Azure infrastructure as code in Bicep, using Azure Verified Modules—pre-built Microsoft modules for deploying Azure resources.

In plain words
What is it for?
Use it to choose and reference AVM modules, set parameters, pin module versions, review outputs, and run Bicep lint checks.
Why use it?
It helps keep infrastructure definitions aligned with Azure recommendations and avoids rewriting common resource configurations.

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-bicep
Clone the repo
git clone --depth 1 https://github.com/github/awesome-copilot
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 494 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.00029 $0.00494
Opus 5 $0.00015 $0.00247
Sonnet 5 $0.00006 $0.00099
Haiku 4.5 $0.00003 $0.00049

Measured 3d ago against content hash f132fbd2b0f9, 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 Bicep 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 3d 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-bicep.agent.md · 47 lines

What it actually says

Azure AVM Bicep mode

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

Discover modules

  • AVM Index: https://azure.github.io/Azure-Verified-Modules/indexes/bicep/bicep-resource-modules/
  • GitHub: https://github.com/Azure/bicep-registry-modules/tree/main/avm/

Usage

  • Examples: Copy from module documentation, update parameters, pin version
  • Registry: Reference br/public:avm/res/{service}/{resource}:{version}

Versioning

  • MCR Endpoint: https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/list
  • Pin to specific version tag

Sources

  • GitHub: https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource}
  • Registry: br/public:avm/res/{service}/{resource}:{version}

Naming conventions

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

Best practices

  • Always use AVM modules where available
  • Pin module versions
  • Start with official examples
  • Review module parameters and outputs
  • Always run bicep lint after making changes
  • Use azure_get_deployment_best_practices tool for deployment guidance
  • Use azure_get_schema_for_Bicep tool for schema validation
  • Use microsoft.docs.mcp tool to look up Azure service-specific guidance
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. 3d ago First seen · 47 lines · 29 tokens per session scan A f132fbd2b0f9

Subscribe to this mod's changes

Azure AVM Bicep mode is an agent published in the GitHub repository github/awesome-copilot (38,502 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 494 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.