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 skills add cacheforge-ai/cacheforge-skills --skill tf-plan-reviewgit clone --depth 1 https://github.com/cacheforge-ai/cacheforge-skillsWrote 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/cacheforge-ai/cacheforge-skills/tf-plan-review)<a href="https://agentmods.dev/skills/cacheforge-ai/cacheforge-skills/tf-plan-review"><img src="https://agentmods.dev/badge/skills/cacheforge-ai/cacheforge-skills/tf-plan-review/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/skills/cacheforge-ai/cacheforge-skills/tf-plan-review"><img src="https://agentmods.dev/badge/skills/cacheforge-ai/cacheforge-skills/tf-plan-review.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.00051 | $0.02704 |
| Opus 5.5 | $0.00020 | $0.01082 |
| Sonnet 5.5 | $0.00010 | $0.00541 |
| Haiku 4.5 | $0.00005 | $0.00270 |
Grade A, and why
tf-plan-review 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 1mo 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terraform Plan Analyzer & Risk Assessor
Analyze terraform plan output and produce an AI-powered risk assessment of every infrastructure change — before you press apply.
This skill is STRICTLY READ-ONLY. It runs terraform plan and terraform validate to analyze changes, but it NEVER runs terraform apply, terraform destroy, terraform import, terraform taint, or any command that modifies infrastructure or state.
Activation
This skill activates when the user mentions:
- "terraform plan", "tf plan", "review plan", "plan review"
- "is this plan safe", "safe to apply", "risk assessment"
- "what will be destroyed", "what changes", "terraform changes"
- "terraform state", "state drift", "drift detection"
- "terraform validate", "validate config", "tf validate"
- "IAM changes", "security group changes", "infrastructure changes"
- "blast radius", "cascade effects", "dependencies"
- "tofu plan", "opentofu" (same workflow, different binary)
Example Prompts
- "Review this terraform plan before I apply"
- "What will be destroyed in this plan?"
- "Is this plan safe to apply?"
- "Show me the state drift"
- "What IAM changes are in this plan?"
- "Validate my terraform config in ~/infra/prod"
- "Run a risk assessment on the terraform plan in /deployments/staging"
- "What's the blast radius if I apply this plan?"
Permissions
permissions:
exec: true # Required to run terraform/tofu CLI
read: true # Read .tf files and plan output
write: false # NEVER writes — strictly read-only analysis
network: true # terraform plan needs provider API access
Terraform Change Types — What the Agent Must Know
Understanding Terraform change types is critical for accurate risk assessment:
Action Types (from plan JSON)
| Action | Meaning | Risk Profile |
|---|---|---|
create |
New resource being added | Generally safe (unless IAM/security) |
update |
Existing resource modified in-place | Moderate (depends on what's changing) |
delete |
Resource being permanently destroyed | DANGEROUS — data loss risk |
replace (delete + create) |
Resource must be destroyed and recreated | DANGEROUS — downtime + data loss |
read |
Data source being refreshed | Safe (read-only) |
no-op |
No changes needed | Safe |
What ships with it
6 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.
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.
- 1mo ago First seen · 268 lines · 51 tokens per session scan A 372388d96f55
tf-plan-review is a skill published in the GitHub repository cacheforge-ai/cacheforge-skills (10 stars, last pushed 8mo ago), licensed MIT. It adds 51 tokens to every session and 2,704 once invoked, about $0.0002 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-31.
Other skills, from other repositories
terraform-iac
Terraform and OpenTofu infrastructure as code best practices - generate HCL configurations, module patterns, state management, CI/CD workflows, and cloud provider templates for AWS, GCP, Azure.
terraform
Terraform infrastructure-as-code workflow patterns: state and environments, module design, safe plan/apply, drift control, and CI guardrails.
IaC Patterns
Authoring patterns for Terraform and Bicep — remote state, module structure, naming, tagging, and plan review — so infrastructure stays reviewable and reproducible.
terraform
A guide to Terraform, a tool that describes and manages cloud infrastructure from configuration files. It covers initialization, formatting, validation, planning, applying changes, state inspection, outputs, and HCL syntax.
terraform-iac
Terraform & Infrastructure as Code: Helps write, review, and structure Terraform configurations, modules, state management, and IaC best practices. Use whenever the user mentions 'terraform', 'IaC', 'infrastructure as code', '.tf files', 'HCL', 'terraform module', 'terraform state', 'terraform plan', 'terraform…
terraform-builder
Build infrastructure as code with Terraform. Covers module design, state management, AWS/GCP/Azure resources, and production-grade practices.