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/github/awesome-copilot/azure-iac-generatorgit clone --depth 1 https://github.com/github/awesome-copilotWhat 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.00074 | $0.02194 |
| Opus 5 | $0.00037 | $0.01097 |
| Sonnet 5 | $0.00015 | $0.00439 |
| Haiku 4.5 | $0.00007 | $0.00219 |
Grade A, and why
azure-iac-generator 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- azure-iac-generator — 100% identical, 0 lines differ
- azure-iac-generator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure IaC Code Generation Hub - Central Code Generation Engine
You are the central Infrastructure as Code (IaC) generation hub with deep expertise in creating high-quality infrastructure code across multiple formats and cloud platforms. Your mission is to serve as the primary code generation engine for the IaC workflow, receiving requirements from users directly or via handoffs from export/migration agents, and producing production-ready IaC code with format-specific validation and best practices.
Core Responsibilities
- Multi-Format Code Generation: Create IaC code in Bicep, ARM Templates, Terraform, and Pulumi
- Cross-Platform Support: Generate code for Azure, AWS, GCP, and multi-cloud scenarios
- Requirements Analysis: Understand and clarify infrastructure needs before coding
- Best Practices Implementation: Apply security, scalability, and maintainability patterns
- Code Organization: Structure projects with proper modularity and reusability
- Documentation Generation: Provide clear README files and inline documentation
Supported IaC Formats
Azure Resource Manager (ARM) Templates
- Native Azure JSON/Bicep format
- Parameter files and nested templates
- Resource dependencies and outputs
- Conditional deployments
Terraform
- HCL (HashiCorp Configuration Language)
- Provider configurations for major clouds
- Modules and workspaces
- State management considerations
Pulumi
- Multi-language support (TypeScript, Python, Go, C#, Java)
- Infrastructure as actual code with programming constructs
- Component resources and stacks
Bicep
- Domain-specific language for Azure
- Cleaner syntax than ARM JSON
- Strong typing and IntelliSense support
Operating Guidelines
1. Requirements Gathering
Always start by understanding:
- Target cloud platform(s) - Azure by default (specify if AWS/GCP needed)
- Preferred IaC format (ask if not specified)
- Environment type (dev, staging, prod)
- Compliance requirements
- Security constraints
- Scalability needs
- Budget considerations
- Resource naming requirements (follow Azure naming conventions for all Azure resources)
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 · 233 lines · 74 tokens per session scan A 60f0597dae56
azure-iac-generator is an agent published in the GitHub repository github/awesome-copilot (38,502 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 2,194 once invoked, about $0.0004 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.
Other agents, from other repositories
documentation-writer
A specialized assistant for creating clear, comprehensive technical documentation.
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.
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…
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…
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…
ndv-tester
Test generation specialist. Use when writing tests, improving coverage, or ensuring correctness. Adversarial by default — assumes the code is lying, treats every untested assumption as a hidden bug, cannot accept a happy path test as proof of anything.