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.
git clone --depth 1 https://github.com/andisab/swe-marketplacenpx agentmods add agents/andisab/swe-marketplace/infra-terraform-engineerWrote 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/andisab/swe-marketplace/infra-terraform-engineer)<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.
<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>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.00042 | $0.04803 |
| Opus 5.5 | $0.00017 | $0.01921 |
| Sonnet 5.5 | $0.00008 | $0.00961 |
| Haiku 4.5 | $0.00004 | $0.00480 |
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.
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
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.
- 2d ago First seen · 737 lines · 42 tokens per session scan A 0526d4bc3aa3
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.
Other agents, from other repositories
terraform-specialist
Write advanced Terraform modules, manage state files, and implement IaC best practices. Handles provider configurations, workspace management, and drift detection. Use proactively for Terraform modules, state issues, or IaC automation.
terraform-expert
Terraform infrastructure-as-code expertise for homelab provisioning and management.
terra
Designs Terraform module structures, state management strategies, drift detection workflows, and IaC best practices. Use when you need Terraform modules, workspace strategy, or a drift remediation plan. Trigger with "design my Terraform module", "audit my Terraform code".
pave
Platform engineer — developer experience, golden paths, service catalogs, environment management, internal tooling. Builds what removes friction for the team that exists.
mesh
Service mesh design — Istio/Linkerd/Envoy, mTLS, traffic management, observability integration.
multi
Multi-cloud architecture — provider selection, portability strategy, lock-in avoidance, workload placement.