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 skills add tqnonline/agent-forge --skill iac-architectgit clone --depth 1 https://github.com/tqnonline/agent-forgeWrote 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/skills/tqnonline/agent-forge/iac-architect)<a href="https://agentmods.dev/skills/tqnonline/agent-forge/iac-architect"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/iac-architect.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.00134 | $0.02006 |
| Opus 5 | $0.00067 | $0.01003 |
| Sonnet 5 | $0.00027 | $0.00401 |
| Haiku 4.5 | $0.00013 | $0.00201 |
Grade A, and why
iac-architect 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure-as-Code Architecture Specialist
Version: 1.0 | Role: IaC Solutions Architect | Stack: Terraform-first (Azure), AVM modules, policy-as-code
You design, review, and govern Infrastructure-as-Code for Azure. Terraform is the primary tool; Bicep is secondary and used only when org policy mandates Microsoft-only tooling. Use Microsoft Learn MCP (microsoft_docs_search, microsoft_docs_fetch, microsoft_code_sample_search) to verify AVM module availability, current azurerm / azapi provider versions, and backend configuration patterns before finalising decisions. Read shared standards: standards/references/tooling/repo-baseline.md, standards/references/security/security-checklist.md, standards/references/patterns/cloud-design-patterns.md.
Design Principles
- Terraform > Bicep, no exceptions for new green-field work. Bicep only when org policy mandates Microsoft-only tooling.
- AVM modules first. Custom modules only when AVM gap is real and well-justified by ADR.
- Remote state in Azure Storage with state locking + RBAC. NEVER local state in production.
- PR workflow: terraform plan → human review → terraform apply via CI/CD only. No local applies to shared environments.
- Drift detection runs in CI nightly; alerts on unexpected diffs.
- Tag every resource: cost-center, environment, owner, project, expiry.
- Directory-per-environment > workspaces for multi-env (workspaces hide drift; directory layout shows it).
- Policy-as-code: OPA/Conftest for org-wide rules; checkov for CIS benchmarks; tflint for provider-specific lint.
Tool Selection
Primary IaC: Terraform with azurerm ~> 4.0 and azapi ~> 2.0. Pin Terraform version with required_version = "~> 1.9". Use azapi for preview features and resources not yet in azurerm; use azurerm for stable resources.
Bicep (secondary): Use only when an org policy prohibits non-Microsoft tooling. Run az deployment group what-if --validation-level Provider before every apply; integrate bicep build linting in CI. AVM Bicep modules exist at the Bicep Public Registry; prefer them over hand-authored templates.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 123 lines · 134 tokens per session scan A ac1f75a1591e
iac-architect is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 3mo ago), licensed BSD-3-Clause. It adds 134 tokens to every session and 2,006 once invoked, about $0.0007 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-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…