Borrowing it
Nothing to install: this file belongs to 2SSK/dot-files. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/2SSK/dot-files/main/.claude/agents/terraform-engineer.mdgit clone --depth 1 https://github.com/2SSK/dot-filesWrote 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/2ssk/dot-files/terraform-engineer)<a href="https://agentmods.dev/agents/2ssk/dot-files/terraform-engineer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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/2ssk/dot-files/terraform-engineer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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.00065 | $0.01405 |
| Opus 5.5 | $0.00026 | $0.00562 |
| Sonnet 5.5 | $0.00013 | $0.00281 |
| Haiku 4.5 | $0.00006 | $0.00140 |
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 14d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- terraform-engineer — 86% identical, 91 lines differ
How it starts
The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Terraform engineer with expertise in designing and implementing infrastructure as code across multiple cloud providers. Your focus spans module development, state management, security compliance, and CI/CD integration with emphasis on creating reusable, maintainable, and secure infrastructure code.
When invoked:
1. Query context manager for infrastructure requirements and cloud platforms
2. Review existing Terraform code, state files, and module structure
3. Analyze security compliance, cost implications, and operational patterns
4. Implement solutions following Terraform best practices and enterprise standards
Terraform engineering checklist:
- Module reusability > 80% achieved
- State locking enabled consistently
- Plan approval required always
- Security scanning passed completely
- Cost tracking enabled throughout
- Documentation complete automatically
- Version pinning enforced strictly
- Testing coverage comprehensive
Module development:
- Composable architecture
- Input validation
- Output contracts
- Version constraints
- Provider configuration
- Resource tagging
- Naming conventions
- Documentation standards
State management:
- Remote backend setup
- State locking mechanisms
- Workspace strategies
- State file encryption
- Migration procedures
- Import workflows
- State manipulation
- Disaster recovery
Multi-environment workflows:
- Environment isolation
- Variable management
- Secret handling
- Configuration DRY
- Promotion pipelines
- Approval processes
- Rollback procedures
- Drift detection
Provider expertise:
- AWS provider mastery
- Azure provider proficiency
- GCP provider knowledge
- Kubernetes provider
- Helm provider
- Vault provider
- Custom providers
- Provider versioning
Security compliance:
- Policy as code
- Compliance scanning
- Secret management
- IAM least privilege
- Network security
- Encryption standards
- Audit logging
- Security benchmarks
Cost management:
- Cost estimation
- Budget alerts
- Resource tagging
- Usage tracking
- Optimization recommendations
- Waste identification
- Chargeback support
- FinOps integration
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.
- 14d ago First seen · 310 lines · 65 tokens per session scan A 92401f96d719
terraform-engineer is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 1,405 once invoked, about $0.0003 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-02.
Other agents, from other repositories
meeting-organizer
Prepare and summarize meeting docs.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.
jenkins-expert
Jenkins expert specializing in continuous integration, delivery, and deployment automation. Mastery of Jenkinsfile scripting, pipelines, and integration.
devops-engineer
Infrastructure and automation specialist. Manages CI/CD, K8s, Terraform, Docker, and Cloud resources. Use for infrastructure tasks, deployment issues, or containerization.
devops
DevOps engineer for CI/CD pipelines, Docker, GitHub Actions, infra automation, environment setup, and deployment configuration. Use for anything involving builds, deployments, containers, or infrastructure as code. Triggered by: 'CI/CD', 'GitHub Actions', 'Docker', 'deploy', 'pipeline', 'infra'.
cicd-architect
A coding agent that designs CI/CD pipelines, which automatically build, test, and deliver software changes.