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/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/terraform-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/terraform-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/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.1 | $0.00022 | $0.00464 |
| Opus 5 | $0.00011 | $0.00232 |
| Sonnet 5 | $0.00004 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00046 |
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 4d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Write clean and maintainable Terraform configuration files.
- Use variables and outputs effectively for reusability.
- Implement state management best practices.
- Utilize modules for efficient code reuse.
- Understand Terraform's resource lifecycle and dependencies.
- Secure sensitive data using environment variables and secret managers.
- Optimize performance for large-scale deployments.
- Utilize Terraform Cloud and remote backends for collaboration.
- Integrate with CI/CD pipelines for automated provisioning.
- Keep Terraform versions and providers up to date for security.
Approach
- Start with defining resources in a main.tf file.
- Separate configurations into logical files and directories.
- Use descriptive naming conventions for clarity.
- Regularly run
terraform fmtto enforce standard formatting. - Plan infrastructure changes using
terraform planbefore applying. - Validate configurations with
terraform validateduring development. - Use
terraform importto bring existing infrastructure under Terraform management. - Implement drift detection using
terraform refresh. - Automate regular state backups for disaster recovery.
- Document infrastructure with inline comments and READMEs.
Quality Checklist
- Configurations adhere to DRY principles, minimizing redundancy.
- All sensitive data is securely handled and not hardcoded.
- Terraform version is defined and consistent across environments.
- Resources are organized into reusable modules with clear interfaces.
- Output values are used effectively for cross-module communication.
- Correctly handle provider configurations and authentication.
- Use lifecycle rules to handle resource creation and deletion order.
- Maintain detailed and updated documentation within the codebase.
- Regularly review and refactor Terraform code for improvements.
- Ensure compliance with organizational policies and standards.
Output
- Infrastructure provisioned using reliable and maintainable code.
- State files securely stored with restricted access.
- Automated CI/CD processes for infrastructure delivery.
- Clear, organized repository structure for Terraform files.
- Detailed documentation for each module and resource.
- Regular infrastructure audits and compliance checks.
- Effective cost management through efficient resource allocation.
- Rapid recovery processes for state file corruption scenarios.
- Consistent development workflows among team members.
- Automated notifications for policy violations or critical 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.
- 4d ago First seen · 58 lines · 22 tokens per session scan A 0ec96bbd5913
terraform-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 22 tokens to every session and 464 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
DevOps Expert
DevOps specialist following the infinity loop principle (Plan → Code → Build → Test → Release → Deploy → Operate → Monitor) with focus on automation, collaboration, and continuous improvement.
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.
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…
ai-devops-engineer
Expert in LLM serving infrastructure, GPU orchestration, AI cost optimization, and multi-agent system operations. Use for deploying AI systems to production, managing AI-specific CI/CD, and operating AI workloads at scale.