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/nitinjain999/platform-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/commands/nitinjain999/platform-skills/terraform)<a href="https://agentmods.dev/commands/nitinjain999/platform-skills/terraform"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/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/nitinjain999/platform-skills/terraform"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/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.00038 | $0.00862 |
| Opus 5 | $0.00019 | $0.00431 |
| Sonnet 5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
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 10d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interactive Wizard (fires when $ARGUMENTS is empty)
When invoked with no arguments, ask before reviewing:
Q1 — What to review?
Paste the Terraform code or plan output, or describe the change
(e.g. "adding an aws_rds_instance", "plan shows 3 resources destroyed", "here's my EKS module"):
Q2 — Focus area? (ask after Q1)
Any specific focus, or full review?
1. Full review — validation pipeline + blast radius + IAM + state impact
2. IAM / security — least privilege, wildcard actions, sensitive vars
3. Blast radius — what gets replaced vs updated, downstream impact
4. Module design — variable validation, output types, provider config
Enter 1–4 [default: 1]:
Then proceed with the review framework below.
You are a senior platform engineer reviewing Terraform.
The input is: $ARGUMENTS
1. Validation Pipeline
Walk through each gate in order. For each, state whether it would pass or fail based on the provided code, and why:
-
terraform fmt -check -recursive— formatting and style -
terraform validate— syntax, type correctness, reference integrity (note: use-backend=falsein CI) -
tflint --recursive— provider-specific rules (invalid instance types, deprecated arguments, missing required_version) -
tfsec . --minimum-severity HIGHorcheckov -d . --framework terraform --compact— security misconfigurationsCheckov deep scan: For full static and plan-level Checkov scanning with bootstrap, multi-cloud provider detection, private module auth, pre-commit generation, and fix mode — use
/platform-skills:checkov.tfsec version note: Flag syntax changed in v1.0+. Check with
tfsec --version.< v1.0: use--minimum-severity HIGH>= v1.0: use--severity HIGH- Drop-in alternative:
trivy config . --severity HIGH
2. Blast Radius
- What cloud resources does this create, modify, or destroy?
- Which resources will be replaced (destroyed and recreated) vs updated in-place?
- What downstream systems depend on these resources?
- What is the impact if this apply fails halfway?
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.
- 10d ago First seen · 94 lines · 38 tokens per session scan A fd43f54da65c
terraform is a command published in the GitHub repository nitinjain999/platform-skills (41 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 862 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-08-30.
Other commands, from other repositories
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.
ia-verify
Run pre-PR verification chain -- build, types, lint, tests, security scan, diff review.
release
Generate changelog, bump version, and create git tag.
ia-report-bug
Report a bug in the whetstone plugin.
cccs-guidance
CCCS assessment process and certified cloud provider guidance.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.