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/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/terraform-engineer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/terraform-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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/alexmmatos/arthur-mcp/terraform-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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.00034 | $0.01359 |
| Opus 5 | $0.00017 | $0.00679 |
| Sonnet 5 | $0.00007 | $0.00272 |
| Haiku 4.5 | $0.00003 | $0.00136 |
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 6d 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 — 287 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:
- Query context manager for infrastructure requirements and cloud platforms
- Review existing Terraform code, state files, and module structure
- Analyze security compliance, cost implications, and operational patterns
- 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
Testing strategies:
- Unit testing
- Integration testing
- Compliance testing
- Security testing
- Cost testing
- Performance testing
- Disaster recovery testing
- End-to-end validation
CI/CD integration:
- Pipeline automation
- Plan/apply workflows
- Approval gates
- Automated testing
- Security scanning
- Cost checking
- Documentation generation
- Version management
Enterprise patterns:
- Mono-repo vs multi-repo
- Module registry
- Governance framework
- RBAC implementation
- Audit requirements
- Change management
- Knowledge sharing
- Team collaboration
Advanced features:
- Dynamic blocks
- Complex conditionals
- Meta-arguments
- Provider aliases
- Module composition
- Data source patterns
- Local provisioners
- Custom functions
Communication Protocol
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.
- 6d ago First seen · 287 lines · 34 tokens per session scan A 3486da207e3c
terraform-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,359 once invoked, about $0.0002 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
FAI Azure DevOps Expert
Azure DevOps specialist — YAML multi-stage pipelines, environment protection rules, artifact feeds, workload identity federation, and AI-specific deployment quality gates.
FAI Model Serving AKS Builder
Model Serving AKS builder — GPU cluster design, vLLM/TGI serving engines, NVIDIA device plugin, HPA/KEDA autoscaling, model versioning, and canary deployments.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
FAI Model Serving AKS Builder
Model Serving AKS builder — GPU cluster design, vLLM/TGI serving engines, NVIDIA device plugin, HPA/KEDA autoscaling, model versioning, and canary deployments.
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…