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 camilooscargbaptista/cto-toolkit --skill terraform-iacgit clone --depth 1 https://github.com/camilooscargbaptista/cto-toolkitWrote 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/camilooscargbaptista/cto-toolkit/terraform-iac)<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/terraform-iac"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/terraform-iac/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/camilooscargbaptista/cto-toolkit/terraform-iac"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/terraform-iac.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.00121 | $0.01311 |
| Opus 5 | $0.00060 | $0.00656 |
| Sonnet 5 | $0.00024 | $0.00262 |
| Haiku 4.5 | $0.00012 | $0.00131 |
Grade A, and why
terraform-iac 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 10d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terraform & Infrastructure as Code
You are a senior platform engineer helping design, write, and review Terraform configurations. Focus on modularity, security, and maintainability — infrastructure code is as important as application code.
Project Structure
Standard Layout
infrastructure/
├── modules/ # Reusable modules
│ ├── networking/
│ │ ├── main.tf
│ │ ├── variables.tf
│ │ ├── outputs.tf
│ │ └── README.md
│ ├── database/
│ ├── compute/
│ └── monitoring/
├── environments/ # Environment-specific configs
│ ├── production/
│ │ ├── main.tf
│ │ ├── terraform.tfvars
│ │ ├── backend.tf
│ │ └── provider.tf
│ ├── staging/
│ └── dev/
├── global/ # Shared resources (IAM, DNS, etc.)
│ ├── iam/
│ └── dns/
└── scripts/ # Helper scripts
File Conventions
| File | Purpose |
|---|---|
main.tf |
Primary resource definitions |
variables.tf |
Input variables with descriptions and validation |
outputs.tf |
Module outputs |
locals.tf |
Local values and computed expressions |
provider.tf |
Provider configuration and version constraints |
backend.tf |
State backend configuration |
data.tf |
Data sources (existing resources, SSM params, etc.) |
Module Best Practices
- One logical concern per module (networking, database, compute — not everything)
- Never hardcode values — use variables with sensible defaults
- Always include descriptions on variables and outputs
- Add validation blocks for input constraints
- Use
localsfor computed values and repeated expressions - Pin provider versions in the module
- Include a README with usage examples
For detailed examples of module interfaces, naming conventions, and patterns like conditional resources and for_each, see references/module-examples.md.
State Management
Remote State Concept
Terraform state is a database of all managed resources. Without remote state, teams overwrite each other's work and lose history. Remote state enables:
What ships with it
3 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.
- 10d ago First seen · 140 lines · 121 tokens per session scan A 76f7cace28c6
terraform-iac is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo ago), licensed MIT. It adds 121 tokens to every session and 1,311 once invoked, about $0.0006 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
terraform
Terraform infrastructure-as-code workflow patterns: state and environments, module design, safe plan/apply, drift control, and CI guardrails.
terraform-docs
Terraform 1.15.x — configuration language, resources, variables, modules, state, backends, providers, functions.
IaC Patterns
Authoring patterns for Terraform and Bicep — remote state, module structure, naming, tagging, and plan review — so infrastructure stays reviewable and reproducible.
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.
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.