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/d-padmanabhan/agent-engineering-handbookWrote 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/commands/d-padmanabhan/agent-engineering-handbook/terraform)<a href="https://agentmods.dev/commands/d-padmanabhan/agent-engineering-handbook/terraform"><img src="https://agentmods.dev/badge/commands/d-padmanabhan/agent-engineering-handbook/terraform/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/commands/d-padmanabhan/agent-engineering-handbook/terraform"><img src="https://agentmods.dev/badge/commands/d-padmanabhan/agent-engineering-handbook/terraform.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.00013 | $0.00398 |
| Opus 5.5 | $0.00005 | $0.00159 |
| Sonnet 5.5 | $0.00003 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
terraform 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 2mo 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.
What it actually says
TERRAFORM MODE ACTIVATED
You are now in TERRAFORM MODE. Any work on Terraform MUST follow:
rules/180-terraform.mdc(module structure, validation, security)rules/100-core.mdc(minimal, maintainable changes)rules/310-security.mdc(no secrets, least privilege)
Use this command when the user asks to:
- Create a new Terraform module
- Modify existing
.tfcode - Review Terraform for correctness/security
Guardrails (mandatory)
- Use
snake_casefor variables/outputs/resources. - Prefer modules and clear inputs/outputs; avoid hardcoding.
- Never commit state files, plan artifacts, or secrets.
- Keep changes minimal and scoped.
Step 0: Determine intent (create vs modify vs review)
Infer intent from the user’s request. If ambiguous, ask ≤3 clarifying questions (target provider, environment, module boundaries).
Create
Produce module-shaped output:
main.tf,variables.tf,outputs.tf,README.md(+examples/when appropriate)- Include validation blocks for inputs where helpful
Modify
- Prefer minimal diffs
- Preserve module interface unless explicitly asked to change it
Review
Prioritize:
- Critical: secrets in variables, overly-permissive IAM, public access exposure, missing encryption, unsafe defaults
- Recommended: missing validation/docs, inconsistent naming, missing tags/labels
- Optional: style and readability
Verification (as applicable):
terraform fmt -check -recursive
terraform validate
pre-commit run --all-files
Done condition
End with:
- Files changed (or “no changes made”)
- How to validate (fmt/validate/lint) and expected behavior
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.
- 2mo ago First seen · 64 lines · 13 tokens per session scan A bd279836d2bc
terraform is a command published in the GitHub repository d-padmanabhan/agent-engineering-handbook (20 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 398 once invoked, about $0.0001 per session on Opus 5.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-30.
terraform compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| terraformd-padmanabhan/agent-engineering-handbook | Command | 20 | yesterday | MIT | A | 13 | Claude Code |
| cost-optimizewshobson/agents | Command | 42k | yesterday | MIT | A | 26 | Claude Code |
| deploybutterbase-ai/butterbase-skills | Command | 535 | 6d ago | MIT | A | 20 | Claude Code |
| envvercel/vercel-plugin | Command | 326 | yesterday | none | A | 35 | Claude Code |
| firebase-publishPierry/harness-kit | Command | 4 | 1mo ago | MIT | A | 20 | Claude Code |
| scanprajapatimehul/claude-aws-cost-saver | Command | 24 | 4mo ago | MIT | A | 6 | Claude Code |
| migrationdatabayt/hogwarts | Command | 18 | 3d ago | none | A | 4 | Claude Code |