AthenodeAthenode

Terraform

Write, test, refactor and review Terraform with a coding agent, using HashiCorp's own skills and registry data, with a hard stop before anything touches real infrastructure.

Start with a Terraform request ("write a module for…", "add tests", "split this configuration into modules", "import these existing resources") or /terraform-plan-review to check a plan for destructive and risky changes before applying it.

Third-party skills, imported unmodified from https://github.com/hashicorp/agent-skills (MPL-2.0; source at that address): terraform-style-guide, terraform-test, refactor-module, terraform-search-import, terraform-stacks, terraform-policy. The terraform-plan-review skill is written by Athenode.

MCP server: HashiCorp's Terraform MCP server (https://github.com/hashicorp/terraform-mcp-server, MPL-2.0) gives current provider, module and policy documentation from the Terraform Registry. It runs locally in Docker and needs no account for the public registry; HCP Terraform and Terraform Enterprise tools need your own token and are not configured here.

Prerequisites: the terraform CLI and Docker. Not affiliated with HashiCorp.

AGENTS.md

Instructions every agent follows
Terraform
  • Never run terraform apply, terraform destroy, terraform import, terraform state subcommands that change state, or terraform force-unlock without an explicit request for that command in that workspace. terraform fmt, validate, init and plan are yours to run.
  • Before anything is applied, show the plan's summary and name every resource that will be destroyed or replaced; say which workspace, account and region it targets.
  • Never edit a state file by hand, and never commit state, plan files, .terraform/ or files holding secrets.

Agents

0
  • Nothing here yet

MCP servers

1
  • terraform

Ready to ship better, together?

Spec it. Decompose it. Ship it. All with your AI agent.

Start for free

Join engineers building with Athenode today.