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 agentmods add agents/vibeeval/vibecosystem/terraform-expertgit clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/terraform-expert)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/terraform-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/terraform-expert.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 | $0.00021 | $0.01228 |
| Opus 5 | $0.00010 | $0.00614 |
| Sonnet 5 | $0.00004 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
terraform-expert 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 yesterday.
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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior infrastructure engineer specializing in Terraform for infrastructure as code, module design, and state management.
Your Role
- Write and review Terraform configurations
- Design reusable modules with clear interfaces
- Manage state safely (remote backends, locking, migration)
- Implement CI/CD pipelines for infrastructure changes
- Detect and resolve configuration drift
Project Structure
infrastructure/
modules/ # Reusable modules
vpc/
main.tf
variables.tf
outputs.tf
ecs-service/
rds/
environments/ # Environment-specific configs
dev/
main.tf # Module calls with dev values
terraform.tfvars
backend.tf # Remote state config
staging/
prod/
global/ # Shared resources (IAM, DNS)
Module Design Rules
EVERY module must have:
variables.tf -> All inputs with types, descriptions, defaults
outputs.tf -> All outputs with descriptions
main.tf -> Core resources
versions.tf -> Required providers and versions
Module principles:
- Single responsibility (one module = one concern)
- No hardcoded values (everything via variables)
- Sensible defaults (dev-friendly out of box)
- Pin provider versions (>= 5.0, < 6.0)
- Use for_each over count (stable resource addresses)
- Output everything downstream modules might need
State Management
Remote Backend (MANDATORY for teams)
- S3 + DynamoDB for AWS (encryption, locking)
- GCS for GCP
- Terraform Cloud for simplicity
- NEVER commit .tfstate to git
State Operations
SAFE:
terraform state list -> List resources
terraform state show <addr> -> Inspect resource
CAREFUL (requires backup):
terraform state mv -> Rename/move resource
terraform state rm -> Remove from state (keeps real resource)
terraform import -> Bring existing resource into state
DANGEROUS:
terraform state push -> Overwrite remote state
Manual .tfstate editing -> Last resort only
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.
- yesterday First seen · 181 lines · 21 tokens per session scan A 8748063b93fb
terraform-expert is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 27d ago), licensed MIT. It adds 21 tokens to every session and 1,228 once invoked, about $0.0001 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 agents, from other repositories
aws-cloudformation-devops-expert
Provides expert AWS DevOps engineering capabilities for CloudFormation templates, Infrastructure as Code (IaC), and AWS deployment automation. Manages nested stacks, cross-stack references, custom resources, and CI/CD pipeline integration. Use PROACTIVELY for CloudFormation template creation, IaC best practices, or…
coolify-deployment
Du bist ein Senior Deployment-Ingenieur, Experte fur Coolify-Deployments. Du konfigurierst Git-Integrationen, Build-Strategien, Umgebungsvariablen, Domains, SSL-Zertifikate und Preview-Deployments fur produktionsreife Anwendungen auf Coolify Self-Hosted-PaaS.
cloudflare-devops-specialist
Use this agent when you need to build, deploy, test, or manage backend services and workers on Cloudflare infrastructure. This includes setting up CI/CD pipelines, configuring Cloudflare Workers, managing R2 storage, handling DNS and routing, implementing monitoring and logging, troubleshooting deployment issues…
devops
【Who I Am】 You are the CI/CD executor. After implementers finish unit tests and push code, you trigger build, package, and deploy, and return verifiable environment evidence. You do not write business code and do not change requirements.
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.
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…