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/HermeticOrmus/LibreUIUX-Claude-CodeWrote 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/hermeticormus/libreuiux-claude-code/terraform-specialist)<a href="https://agentmods.dev/agents/hermeticormus/libreuiux-claude-code/terraform-specialist"><img src="https://agentmods.dev/badge/agents/hermeticormus/libreuiux-claude-code/terraform-specialist/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/hermeticormus/libreuiux-claude-code/terraform-specialist"><img src="https://agentmods.dev/badge/agents/hermeticormus/libreuiux-claude-code/terraform-specialist.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.00077 | $0.01638 |
| Opus 5 | $0.00039 | $0.00819 |
| Sonnet 5 | $0.00015 | $0.00328 |
| 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 9d 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
98% identical to cicd-automation-terraform-specialist — 27 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.
- 9d ago First seen · 138 lines · 77 tokens per session scan A 89f41c979858
terraform-specialist is an agent published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (101 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 1,638 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to cicd-automation-terraform-specialist, differing in 27 lines, and is treated as a copy.
Other agents, from other repositories
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
ssh-admin
Linux server admin: SSH, Docker, systemd, Nginx, SSL. Triggers: ssh admin, server management.
gcp-pattern-finder
Finds patterns and correlations across GCP services. Correlates logs by traceid, builds timelines, detects cascade failures, and identifies relationships between events. Use when investigating distributed system issues or cross-service patterns.
k8s-pattern-finder
Finds patterns and correlations across Kubernetes resources. Detects common failure modes, identifies affected resources, analyzes deployment impacts, and discovers infrastructure issues. Use when investigating cluster-wide or multi-resource problems.
gcp-analyzer
Analyzes GCP logs and resources to diagnose issues. Deep dives into service behavior, filters logs to relevant entries, and identifies root causes. Use when investigating a specific service or issue.