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.
git 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/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/vibeeval/vibecosystem/terraform-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/terraform-expert.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.00021 | $0.01228 |
| Opus 5.5 | $0.00008 | $0.00491 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago First seen · 181 lines · 21 tokens per session scan A 8748063b93fb
terraform-expert is an agent published in the GitHub repository vibeeval/vibecosystem (539 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 1,228 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
cicd-automation-terraform-specialist
Expert Terraform/OpenTofu specialist mastering advanced IaC automation, state management, and enterprise infrastructure patterns. Handles complex module design, multi-cloud deployments, GitOps workflows, policy as code, and CI/CD integration. Covers migration strategies, security best practices, and modern IaC…
github-actions-expert
Use this agent when you need expert GitHub Actions workflow development, CI/CD pipeline optimization, and security hardening. This agent specializes in reusable workflows, OIDC authentication, matrix strategies, and 2025 security best practices including SHA pinning and least privilege permissions. Examples: Context…
deployment-expert
Specializes in Vercel deployment strategies, CI/CD pipelines, preview URLs, production promotions, rollbacks, environment variables, and domain configuration. Use when troubleshooting deployments, setting up CI/CD, or optimizing the deploy pipeline.
creo-cloudflare-cli
Cloudflare Wrangler expert for Workers, Pages, R2, D1, KV, deployments, and secrets management.
creo-railway-cli
Railway CLI expert for projects, services, deployments, databases, and environment variables.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.