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 niels-emmer/myace --skill iac-patternsgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/iac-patterns)<a href="https://agentmods.dev/skills/niels-emmer/myace/iac-patterns"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/iac-patterns/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/skills/niels-emmer/myace/iac-patterns"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/iac-patterns.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.00037 | $0.00639 |
| Opus 5 | $0.00018 | $0.00319 |
| Sonnet 5 | $0.00007 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
IaC Patterns 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 5d 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Infrastructure-as-code fails in predictable ways: state drift, unreadable modules, resources nobody can name or attribute, and plans nobody actually reads. This skill is the working checklist for authoring Terraform and Bicep that stays reviewable and reproducible over time.
When to use it
Every time you write or modify IaC — a new resource, a module, a state change, or a refactor. Reach for it explicitly when starting work in an unfamiliar codebase or when you're about to introduce a pattern that doesn't match its neighbors.
Steps / checklist
- Remote state with locking. State lives in a remote backend (Terraform) or a deployment stack (Bicep) with locking enabled. Local state is not acceptable for anything shared or persistent. Never commit state files.
- Module structure. Split by concern (networking, compute, data, identity), not by resource type. A module should encapsulate a deployable unit with a clear interface — inputs, outputs, and invariants — not a grab-bag of related resources.
- Naming and tagging. Every resource follows the project's naming convention and carries team + cost-center tags (see the
resource-namingskill in the iac-expert collection for a template). Names are deterministic from inputs, not hand-assigned. - Private by default. Every resource starts network-isolated. No public IP,
0.0.0.0/0ingress, or public bucket ACL without a documented exception. - Managed identity over secrets. Use workload identity (Azure Managed Identity, AWS IAM roles, GCP Workload Identity Federation) over API keys or connection strings. Static secrets only when the target has no identity-federation option.
- Plan review discipline. Read the plan output before applying: does it create/destroy resources the task didn't ask for? Is the diff scoped to the change? A plan you haven't read is a plan you haven't approved.
- Drift detection. Treat drift as a defect. Prefer
plan/validatein CI and scheduled drift checks over discovering divergence at incident time. - Version pinning. Pin provider and module versions. Unpinned providers make builds non-reproducible and plans unpredictable.
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.
- 5d ago First seen · 30 lines · 37 tokens per session scan A 9b6f67ac2a92
IaC Patterns is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 639 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
terraform
Terraform infrastructure-as-code workflow patterns: state and environments, module design, safe plan/apply, drift control, and CI guardrails.
terraform
A guide to Terraform, a tool that describes and manages cloud infrastructure from configuration files. It covers initialization, formatting, validation, planning, applying changes, state inspection, outputs, and HCL syntax.
terraform-iac
Terraform and OpenTofu infrastructure as code best practices - generate HCL configurations, module patterns, state management, CI/CD workflows, and cloud provider templates for AWS, GCP, Azure.
infrastructure-as-code-guardian
Universal Infrastructure as Code (IaC) agent skill for authoring, securing, and managing cloud infrastructure across Terraform, Pulumi, CloudFormation, Ansible, and Bicep. Provides cross-tool security hardening, state management best practices, cost optimization, drift detection, and CI/CD integration. Covers AWS…
terraform-iac
Terraform & Infrastructure as Code: Helps write, review, and structure Terraform configurations, modules, state management, and IaC best practices. Use whenever the user mentions 'terraform', 'IaC', 'infrastructure as code', '.tf files', 'HCL', 'terraform module', 'terraform state', 'terraform plan', 'terraform…
tf-plan-review
Analyze Terraform plans for risk before you apply. Classifies every change as safe, moderate, dangerous, or critical. Detects destroys, IAM changes, data-loss risks, and blast radius. Entirely read-only — never runs apply.