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/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/azure-iac-generator)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/azure-iac-generator"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/azure-iac-generator.svg" alt="Measured on agentmods" 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.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 8d 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-iac-generator — 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.
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.
- 8d ago First seen · 233 lines · 74 tokens per session scan A 60f0597dae56
azure-iac-generator is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 4d ago), licensed ISC. 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. It is 100% identical to azure-iac-generator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
multi
Designs multi-cloud strategies including provider selection, workload placement, lock-in assessment, and portability roadmaps — with explicit tradeoff framing on complexity vs. benefit. Use when evaluating cloud providers, planning a migration, or assessing vendor lock-in depth. Trigger with "design our multi-cloud…
issue-feature-review
Review GitHub feature requests with constructive skepticism. Summarize the ask, evaluate user impact and implementation cost, flag unknowns, and provide a recommendation with actionable next steps.
scout
Cheap mechanical retrieval — locate files and symbols, list dependencies and versions, run a single command or test and capture output, extract specific facts from specific files. Use for questions with a definite answer that require no interpretation.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.