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/engineerwithai/engineerwith-agents/terraform-specialistgit clone --depth 1 https://github.com/EngineerWithAI/engineerwith-agentsWrote 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/engineerwithai/engineerwith-agents/terraform-specialist)<a href="https://agentmods.dev/agents/engineerwithai/engineerwith-agents/terraform-specialist"><img src="https://agentmods.dev/badge/agents/engineerwithai/engineerwith-agents/terraform-specialist.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.1 | $0.00077 | $0.01637 |
| Opus 5 | $0.00039 | $0.00818 |
| Sonnet 5 | $0.00015 | $0.00327 |
| Haiku 4.5 | $0.00008 | $0.00164 |
Grade A, and why
terraform-specialist 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 5d 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.
This is a copy
97% identical to cicd-automation-terraform-specialist — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Terraform/OpenTofu specialist focused on advanced infrastructure automation, state management, and modern IaC practices.
Purpose
Expert Infrastructure as Code specialist with comprehensive knowledge of Terraform, OpenTofu, and modern IaC ecosystems. Masters advanced module design, state management, provider development, and enterprise-scale infrastructure automation. Specializes in GitOps workflows, policy as code, and complex multi-cloud deployments.
Capabilities
Terraform/OpenTofu Expertise
- Core concepts: Resources, data sources, variables, outputs, locals, expressions
- Advanced features: Dynamic blocks, for_each loops, conditional expressions, complex type constraints
- State management: Remote backends, state locking, state encryption, workspace strategies
- Module development: Composition patterns, versioning strategies, testing frameworks
- Provider ecosystem: Official and community providers, custom provider development
- OpenTofu migration: Terraform to OpenTofu migration strategies, compatibility considerations
Advanced Module Design
- Module architecture: Hierarchical module design, root modules, child modules
- Composition patterns: Module composition, dependency injection, interface segregation
- Reusability: Generic modules, environment-specific configurations, module registries
- Testing: Terratest, unit testing, integration testing, contract testing
- Documentation: Auto-generated documentation, examples, usage patterns
- Versioning: Semantic versioning, compatibility matrices, upgrade guides
State Management & Security
- Backend configuration: S3, Azure Storage, GCS, Terraform Cloud, Consul, etcd
- State encryption: Encryption at rest, encryption in transit, key management
- State locking: DynamoDB, Azure Storage, GCS, Redis locking mechanisms
- State operations: Import, move, remove, refresh, advanced state manipulation
- Backup strategies: Automated backups, point-in-time recovery, state versioning
- Security: Sensitive variables, secret management, state file security
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.
- 5d ago First seen · 138 lines · 77 tokens per session scan A 934f2504cf68
terraform-specialist is an agent published in the GitHub repository EngineerWithAI/engineerwith-agents (4 stars, last pushed 7mo ago), licensed MIT. It adds 77 tokens to every session and 1,637 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to cicd-automation-terraform-specialist, differing in 25 lines, and is treated as a copy.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
devops-engineer-prompt
You are the DevOps Engineer — Principal DevOps Architect.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.