infrastructure-as-code

infrastructure-as-code is a skill for Claude Code, Codex from vignesh2027/AI-AGENT-SKILLS. It costs 17 tokens per session (633 once invoked), scanned A, original, MIT.

A workflow for managing cloud and other infrastructure as code, meaning configuration stored in version-controlled files. Changes are planned, reviewed, tested, and applied in stages.

In plain words
What is it for?
Writing desired infrastructure state, reviewing Terraform, Pulumi, or CloudFormation plans, checking the possible impact, and safely changing production resources.
Why use it?
It reduces configuration drift and makes infrastructure changes reproducible and reviewable. Plan output also reveals unexpected replacements, deletions, or exposed secrets before deployment.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Writing desired infrastructure state, reviewing Terraform, Pulumi, or CloudFormation plans, checking the possible impact, and safely changing production resources.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vignesh2027/ai-agent-skills/infrastructure-as-code
Install

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.

Any agent
npx skills add vignesh2027/AI-AGENT-SKILLS --skill infrastructure-as-code
Clone the repo
git clone --depth 1 https://github.com/vignesh2027/AI-AGENT-SKILLS

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for infrastructure-as-code

README.md
[![agentmods](https://agentmods.dev/badge/skills/vignesh2027/ai-agent-skills/infrastructure-as-code.svg)](https://agentmods.dev/skills/vignesh2027/ai-agent-skills/infrastructure-as-code)
Your own site
<a href="https://agentmods.dev/skills/vignesh2027/ai-agent-skills/infrastructure-as-code"><img src="https://agentmods.dev/badge/skills/vignesh2027/ai-agent-skills/infrastructure-as-code.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 633 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00633
Opus 5 $0.00009 $0.00316
Sonnet 5 $0.00003 $0.00127
Haiku 4.5 $0.00002 $0.00063

Measured 8d ago against content hash 0c015f65d0bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

infrastructure-as-code 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 8d 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.

skills/infrastructure-as-code/SKILL.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview

Infrastructure defined by hand is infrastructure that drifts, that can't be reviewed, and that can't be reproduced. This skill enforces that all infrastructure is version-controlled code with the same discipline as application code: specs, reviews, tests, and staged deployment.

When to Use

  • Before provisioning any cloud resource
  • Before modifying production infrastructure
  • When investigating a drift between expected and actual infrastructure state

Process

Step 1: Define the desired state first

Write the IaC code that represents the desired state before applying it. Terraform plan / Pulumi preview / CloudFormation change set must be reviewed before apply.

Step 2: Review the plan output

The plan is the diff for infrastructure changes. Review it as carefully as a code diff:

  • Are only expected resources being created/modified/destroyed?
  • Are any resources being replaced (destroy + create) that should only be modified?
  • Are sensitive values being exposed in the plan output?

Step 3: Blast radius analysis

Before applying:

  • What is the maximum impact if this change fails?
  • Does this change affect production traffic?
  • Does this change touch the database, auth system, or network layer?
  • Is the rollback procedure documented?

High blast radius changes require explicit approval from a second engineer.

Step 4: State management

  • Use remote state with locking (never local state for team environments)
  • Never manually modify state files
  • Version state file changes
  • Test: can you destroy and recreate from scratch?

Step 5: Drift detection

Run drift detection on a schedule. If the actual state diverges from the IaC state, investigate and resolve — don't let drift accumulate.

Step 6: Secrets management

  • No secrets in IaC code or state files
  • Use: Vault, AWS Secrets Manager, GCP Secret Manager, or similar
  • Rotate secrets via IaC, not manually

Step 7: Test the IaC

  • Unit tests for modules (Terratest, Pulumi testing)
  • Integration tests: deploy to a non-prod environment and verify
  • Destroy test: can you tear it down and recreate it?

Read the full file on GitHub · 78 lines

Changes

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.

  1. 8d ago First seen · 78 lines · 17 tokens per session scan A 0c015f65d0bf

Subscribe to this mod's changes

infrastructure-as-code is a skill published in the GitHub repository vignesh2027/AI-AGENT-SKILLS (2 stars, last pushed 10d ago), licensed MIT. It adds 17 tokens to every session and 633 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.