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.
git clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/kimiski33/awesome-copilot/azure-verified-modules-bicep)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/azure-verified-modules-bicep"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/azure-verified-modules-bicep/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/azure-verified-modules-bicep"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/azure-verified-modules-bicep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00029 | $0.00494 |
| Opus 5 | $0.00015 | $0.00247 |
| Sonnet 5 | $0.00006 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00049 |
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 9d 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.
This is a copy
100% identical to Azure AVM Bicep mode — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 lintafter making changes - Use
azure_get_deployment_best_practicestool for deployment guidance - Use
azure_get_schema_for_Biceptool for schema validation - Use
microsoft.docs.mcptool to look up Azure service-specific guidance
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.
- 9d ago First seen · 47 lines · 29 tokens per session scan A f132fbd2b0f9
Azure AVM Bicep mode is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 3d ago), 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. It is 100% identical to Azure AVM Bicep mode, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.