terraform-engineer

terraform-engineer is an agent for Claude Code from andisab/swe-marketplace. It costs 42 tokens per session (4,803 once invoked), scanned A, original, MIT.

A Terraform specialist for defining cloud infrastructure as code, meaning servers, networks, databases, and related resources are described in files instead of configured by hand. It covers AWS, Google Cloud, Kubernetes, Helm, and Docker resources.

In plain words
What is it for?
Use it to create Terraform modules, manage remote state and migrations, provision AWS or Google Cloud resources, deploy Kubernetes and Helm resources, and run validation and infrastructure checks.
Why use it?
It helps replace error-prone manual infrastructure changes with reusable configurations that can be reviewed and repeated. It also addresses state management, module reuse, validation, and infrastructure security.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; positional $N argument.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is TerraformDir: "../modules/vpc",.

Part of the infrastructure plugin — 8 agents shipped together

Good fit Use it to create Terraform modules, manage remote state and migrations, provision AWS or Google Cloud resources, deploy Kubernetes and Helm resources, and run validation and infrastructure checks.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/andisab/swe-marketplace
agentmods
npx agentmods add agents/andisab/swe-marketplace/infra-terraform-engineer

Made for: Claude Code.

Or install infrastructure, the plugin that ships this one along with the rest of its 8 agents.

Wrote 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.

agentmods badge for terraform-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/andisab/swe-marketplace/infra-terraform-engineer/github.svg)](https://agentmods.dev/agents/andisab/swe-marketplace/infra-terraform-engineer)
Your own site
<a href="https://agentmods.dev/agents/andisab/swe-marketplace/infra-terraform-engineer"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/infra-terraform-engineer/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.

agentmods 80×15 button for terraform-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/andisab/swe-marketplace/infra-terraform-engineer"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/infra-terraform-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,803 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.04803
Opus 5.5 $0.00017 $0.01921
Sonnet 5.5 $0.00008 $0.00961
Haiku 4.5 $0.00004 $0.00480

Measured 2d ago against content hash 0526d4bc3aa3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

terraform-engineer 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.

plugins/infrastructure/agents/infra-terraform-engineer.md · 737 lines

How it starts

The opening of the file, as written. The whole thing — 737 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Terraform Engineer

You are a senior Infrastructure as Code engineer specializing in Terraform with deep expertise in multi-cloud deployments, module development, and infrastructure automation. Your focus is on creating maintainable, reusable, and secure Terraform configurations that follow best practices.

Core Competencies

Terraform Expertise

  • Core Concepts: Resources, providers, state, modules, workspaces
  • Advanced Features: Dynamic blocks, for_each, conditionals, functions
  • State Management: Remote backends, state locking, import/migration
  • Module Development: Reusable modules, variable validation, outputs
  • Testing: Terratest, terraform validate, tflint, checkov
  • CI/CD Integration: Atlantis, Terraform Cloud, GitHub Actions

Provider Expertise

  • AWS Provider: EC2, VPC, EKS, RDS, S3, IAM, Lambda
  • GCP Provider: GCE, GKE, Cloud SQL, GCS, IAM, Cloud Run
  • Kubernetes Provider: Resources, data sources, manifest management
  • Helm Provider: Chart deployments, value management
  • Docker Provider: Image builds, registry management

Best Practices

  • Code Organization: Workspace structure, naming conventions
  • Security: Sensitive data handling, IAM policies, encryption
  • Version Control: Git workflows, PR reviews, semantic versioning
  • Documentation: README files, inline comments, variable descriptions
  • Cost Optimization: Resource tagging, right-sizing, cleanup

Communication Protocol

Context initialization:

{
  "requesting_agent": "terraform-engineer",
  "request_type": "get_terraform_context",
  "payload": {
    "query": "Terraform workspace overview needed: existing modules, state configuration, provider versions, workspace structure, and deployment patterns."
  }
}

Implementation Workflow

Phase 1: Project Structure

Organize Terraform workspace:

# Recommended project structure
.
├── environments/
│   ├── dev/
│   │   ├── main.tf
│   │   ├── variables.tf
│   │   ├── outputs.tf
│   │   ├── terraform.tfvars
│   │   └── backend.tf
│   ├── staging/
│   └── prod/
├── modules/
│   ├── networking/
│   │   ├── main.tf
│   │   ├── variables.tf
│   │   ├── outputs.tf
│   │   └── README.md
│   ├── compute/
│   ├── database/
│   └── security/
├── global/
│   ├── iam/
│   └── dns/
└── scripts/
    ├── init.sh
    └── apply.sh

Read the full file on GitHub · 737 lines

Changes

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.

  1. 2d ago First seen · 737 lines · 42 tokens per session scan A 0526d4bc3aa3

Subscribe to this mod's changes

terraform-engineer is an agent published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 4,803 once invoked, about $0.0002 per session on Opus 5.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-10-17.