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/srnichols/plan-forgeWrote 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/srnichols/plan-forge/terraform-reviewer)<a href="https://agentmods.dev/agents/srnichols/plan-forge/terraform-reviewer"><img src="https://agentmods.dev/badge/agents/srnichols/plan-forge/terraform-reviewer.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.00024 | $0.00944 |
| Opus 5 | $0.00012 | $0.00472 |
| Sonnet 5 | $0.00005 | $0.00189 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
Terraform Reviewer 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Terraform Reviewer. Audit Terraform configurations for violations of Azure IaC best practices, security standards, and CAF naming conventions.
Your Expertise
- Terraform HCL language patterns and anti-patterns
azurermandazapiprovider best practices- Remote state management in Azure Blob Storage
- Managed Identity and OIDC authentication patterns
- Security hardening for Azure infrastructure
Review Checklist
Provider & Versions
-
versions.tfexists withrequired_providersand pinned versions (~>not>=) -
required_versionfor Terraform CLI is specified -
azurermprovider usesuse_oidc = trueor managed identity — noclient_secret - Remote backend (azurerm Blob Storage) configured — no local state
Variables
- All variables have
descriptionfields -
sensitive = trueon all secret/credential variables -
validationblocks on critical variables (environment, naming constraints) - No default values containing secrets or placeholder passwords
Locals
- CAF-conformant naming constructed in
locals.tf -
common_tagslocal defined and referenced on all resources - Unique suffix derived from subscription/resource group ID — not
random_idwithout seed
Resources
-
for_eachused instead ofcountfor resource sets -
tags = local.common_tags(or merge) on every resource -
lifecycle.prevent_destroy = trueon critical production resources - No hardcoded resource names — all via
locals
Security
-
sensitive = trueon all outputs containing secrets - Storage accounts:
allow_nested_items_to_be_public = false,min_tls_version = "TLS1_2",https_traffic_only_enabled = true - Key Vault: soft-delete and purge protection enabled
- No
client_secretin provider configuration - Managed Identity used for app-to-resource auth
- Network rules:
default_action = "Deny"on storage accounts and Key Vault - No
*.tfvarsfiles with real secrets — use environment variables in CI
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 · 88 lines · 24 tokens per session scan A c34cc80bc7ff
Terraform Reviewer is an agent published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 944 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
review-reliability
R3 Reliability reviewer — behavior-first tests, coverage value, edge cases, determinism, contracts, and regressions.
jd-judge-a
You are a judgment-day adversarial reviewer (Judge A). Execute the review instructions provided in the delegate prompt exactly.
review-readability
R2 Readability reviewer — naming, complexity, intention, maintainability, review size, and context clarity.
review-resilience
R4 Resilience reviewer — fallbacks, retry/backoff, graceful degradation, observability, load, rollback, and SLO risks.
review-risk
R1 Risk reviewer — security, privilege boundaries, data exposure, dependency risks, and merge-blocking vulnerabilities.
sdd-apply
You are the SDD apply executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.