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.
npx agentmods add skills/fmind/dot/terraform-stacknpx skills add fmind/dot --skill terraform-stackgit clone --depth 1 https://github.com/fmind/dotWrote 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/skills/fmind/dot/terraform-stack)<a href="https://agentmods.dev/skills/fmind/dot/terraform-stack"><img src="https://agentmods.dev/badge/skills/fmind/dot/terraform-stack.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 | $0.00044 | $0.01693 |
| Opus 5 | $0.00022 | $0.00847 |
| Sonnet 5 | $0.00009 | $0.00339 |
| Haiku 4.5 | $0.00004 | $0.00169 |
Grade A, and why
terraform-stack 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 yesterday.
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terraform / OpenTofu Stack Standard
Canonical infrastructure as code with OpenTofu (the open-source Terraform fork; the binary is tofu). Reserve HashiCorp terraform for repositories that require a BSL-licensed feature or an employer mandate, and mention the deviation.
1. Core Stack
- Engine: OpenTofu via mise (
opentofutool,tofubinary); everyterraform {}block and.tffile works unchanged, and OpenTofu adds client-side state encryption. - Tasks and hooks: mise.toml exposes the canonical vocabulary per mise —
checkfans out to format, validate, lint (tflint), scan (trivy), and leaks; lefthook.yml wires the hooks per lefthook. - Docs:
terraform-docsinjects the inputs/outputs table intoREADME.mdbetween<!-- BEGIN_TF_DOCS -->/<!-- END_TF_DOCS -->markers, configured by terraform-docs.yml. - Apply is manual:
buildproducestmp/plan.tfplan; applying it is a deliberate human step (tofu apply tmp/plan.tfplan), never a task or hook.
2. Project Scaffolding Workflow
- Information: define the project
Slug, GCPProject ID, and defaultRegion. - Config files:
- mise.toml and lefthook.yml.
.tflint.hclfrom tflint.hcl — pins the terraform preset and the GCP ruleset release..terraform-docs.ymlfrom terraform-docs.yml, plus theTF_DOCSmarkers inREADME.md.dprint.jsonper dprint,.gitignorefrom gitignore,LICENSEper project-license.
- Sources (flat root module; no
modules/tree until a unit is reused):- versions.tf — version constraints, provider pins, and the commented GCS backend and encryption blocks.
- main.tf, variables.tf (typed, validated inputs), outputs.tf.
- terraform.example.tfvars — non-secret example and static-scan values; replace the project ID before planning.
tests/main.tftest.hclfrom main.tftest.hcl — plan-only native tests.
- Validate:
git init --initial-branch=main, thenmise run install,mise run format,mise run check,mise run test— green without cloud access because the backend ships commented and tests run in plan mode. - Lock providers: commit
.terraform.lock.hcl; on multi-platform teams runtofu providers lock -platform=linux_amd64 -platform=darwin_arm64. - Promote the backend: once real state exists, create the versioned GCS bucket (commands in versions.tf), uncomment
backend "gcs", and re-runmise run install;tofu initmigrates local state after a prompt.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/gitignore 366 B
- references/lefthook.yml 529 B
- references/main.tf 466 B
- references/main.tftest.hcl 566 B
- references/mise.toml 2.8 KB
- references/outputs.tf 129 B
- references/terraform-docs.yml 148 B
- references/terraform.example.tfvars 142 B
- references/tflint.hcl 346 B
- references/variables.tf 581 B
- references/versions.tf 1.3 KB
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.
- yesterday First seen · 73 lines · 44 tokens per session scan A bd85d8b81f71
terraform-stack is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,693 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 skills, from other repositories
cloud-run
Deploy container services to Google Cloud Run with Artifact Registry, keyless CI identity, Secret Manager, ko, or Dockerfiles.
google-cloud-operations
Operate Google Cloud with gcloud: pin account, configuration, project, and billing context for IAM, APIs, logs, and audits outside deployment.
terraform-stack
Canonical infrastructure-as-code stack — OpenTofu-first with tflint, trivy config scans, terraform-docs, native tests, and GCS state. Use for any Terraform or OpenTofu work.
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.