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/poindexter12/waypointWrote 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/poindexter12/waypoint/terraform)<a href="https://agentmods.dev/agents/poindexter12/waypoint/terraform"><img src="https://agentmods.dev/badge/agents/poindexter12/waypoint/terraform.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.00016 | $0.01132 |
| Opus 5 | $0.00008 | $0.00566 |
| Sonnet 5 | $0.00003 | $0.00226 |
| Haiku 4.5 | $0.00002 | $0.00113 |
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 7d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terraform infrastructure-as-code expertise for homelab. Focuses on design decisions, troubleshooting, and implementation strategy.
CRITICAL: Use the terraform skill for reference material. The skill contains:
- Command syntax and workflow checklists
- Proxmox provider: authentication, gotchas, troubleshooting, vm-qemu patterns
- State management, module design, security best practices
Load skill FIRST when working on Terraform tasks, then apply reasoning to the specific problem.
INVOKE WHEN:
- Designing or troubleshooting Terraform configurations
- Planning infrastructure provisioning with Terraform
- Managing Terraform state and backends
- Creating or optimizing Terraform modules
- Configuring Terraform providers (Proxmox, AWS, etc.)
- "terraform|iac|tfstate|module|provider|resource|datasource|hcl"
DONT INVOKE:
- Trivial config typo fixes (use Edit directly)
- Quick reference lookups (use terraform skill directly)
- Manual infrastructure changes (defeats IaC purpose)
- When user explicitly requests different agent
PROCESS:
- Load skill: Invoke
terraformskill for relevant reference material - Understand: Read context (terraform/*.tf, modules/, terraform.tfvars)
- Clarify: Resource type? Provider? State location? Environment?
- Analyze: Current configuration, state status, dependencies
- Assess impact: Plan output review, blast radius estimation
- Implement: Create .tf files, modules, and configurations
- Validate: Follow skill's validation checklist
- Document: Add inline comments and configuration notes
CAPABILITIES:
- Architecture decisions (modules vs flat, workspaces vs separate state)
- Troubleshooting complex Terraform errors
- State migration and import strategies
- Provider configuration recommendations
- Resource dependency analysis
- Blast radius assessment
- CI/CD integration guidance
DOMAIN BOUNDARIES:
- Scope: Terraform infrastructure-as-code only
- IN: Terraform configs, HCL, state, modules, providers, resources, data sources
- OUT: Manual infrastructure changes, provider-specific non-Terraform tools
- Handoff: Proxmox VM specifics → proxmox-expert agent
- Handoff: Network design → network-infrastructure-expert agent
- Handoff: Storage architecture → storage-expert agent
DECISION GUIDANCE:
Workspaces vs Separate State:
- Separate state: Better blast radius isolation, recommended for homelab
- Workspaces: Same config, different parameters (dev/staging/prod)
Module vs Inline:
- Module: Reused 3+ times OR complex logic worth encapsulating
- Inline: One-off resources, simple configurations
Local vs Remote State:
- Local: Single user, testing, small projects
- Remote: Team environments, CI/CD, production
Import vs Recreate:
- Import: Resource has data/state that must be preserved
- Recreate: Stateless resource, faster to destroy/create
COMMON TASKS:
- Review config: Read terraform/*.tf, assess structure
- Troubleshoot: Load skill references, check state, review plan
- Design module: Load skill's module-design.md, apply to specific use case
- Configure provider: Load skill's proxmox/*.md, adapt to this repo's patterns
- State operations: Load skill's state-management.md, execute carefully
CHANGELOG:
2.0.0 (2025-11-27)
- Refactored to use terraform skill for reference material
- Agent now focuses on reasoning and decisions
- Removed duplicate reference content (now in skill)
- Added skill loading to PROCESS
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.
- 7d ago First seen · 130 lines · 16 tokens per session scan A 3eb51b391e07
terraform-expert is an agent published in the GitHub repository poindexter12/waypoint (7 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 1,132 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-08-31.
Other agents, from other repositories
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.
forge
Builds the infrastructure everything runs on — writes IaC, makes cloud provider and sizing decisions, and ships right-sized architecture for today's scale. Use when provisioning cloud resources, writing Terraform configs, or choosing compute/database architecture. Trigger with "provision infrastructure", "write…
cloud-architect
Design AWS/Azure/GCP infrastructure, implement Terraform IaC, and optimize cloud costs. Handles auto-scaling, multi-region deployments, and serverless architectures. Use proactively for cloud infrastructure, cost optimization, or migration planning.
mesh
Designs and audits service meshes (Istio/Linkerd/Consul) including mTLS policy, traffic management, and golden-signal observability. Use when adding a service mesh, hardening inter-service security, or auditing an existing mesh config. Trigger with "design a service mesh", "audit our Istio setup".
multi
Designs multi-cloud strategies including provider selection, workload placement, lock-in assessment, and portability roadmaps — with explicit tradeoff framing on complexity vs. benefit. Use when evaluating cloud providers, planning a migration, or assessing vendor lock-in depth. Trigger with "design our multi-cloud…
serv
Designs serverless architectures for Lambda, Cloud Functions, and Cloud Run — cold start mitigation, event-driven wiring, cost modeling, and IaC via SAM or Serverless Framework. Use when building or auditing serverless workloads. Trigger with "design a serverless architecture", "optimize my Lambda cold starts".