Atmos is an infrastructure runtime that coordinates tools such as Terraform, OpenTofu, Kubernetes, Helm, Packer, Ansible, and containers through consistent commands and configuration. It is for teams running cloud infrastructure on laptops, in CI, or through AI agents across environments and regions. Its catalogue entries provide skills, agents, commands, and other add-ons for Atmos workflows.
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 cloudposse/atmos --skill atmos-terraform-state-migrationsgit clone --depth 1 https://github.com/cloudposse/atmosWrote 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/cloudposse/atmos/atmos-terraform-state-migrations)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-terraform-state-migrations"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-terraform-state-migrations/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/cloudposse/atmos/atmos-terraform-state-migrations"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-terraform-state-migrations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.01571 |
| Opus 5.5 | $0.00027 | $0.00628 |
| Sonnet 5.5 | $0.00013 | $0.00314 |
| Haiku 4.5 | $0.00007 | $0.00157 |
Grade A, and why
atmos-terraform-state-migrations 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Terraform State Migrations
Use this skill when creating or reviewing Terraform state migrations for Atmos components. Atmos delegates state
migrations to tfmigrate. It runs tfmigrate in the same component context as atmos terraform plan and apply.
Before tfmigrate runs, Atmos performs auth identity setup, source and workdir provisioning, backend and varfile
generation, Terraform init, workspace selection, toolchain resolution, and TFMIGRATE_EXEC_PATH setup.
For migration HCL syntax and examples, load references/tfmigrate-migration-patterns.md.
Start With Resolved Context
Never guess stack names, component names, workspaces, backend paths, or state addresses.
atmos describe component <component> -s <stack>
atmos terraform migrate list <component> -s <stack>
atmos terraform state list <component> -s <stack>
Use the resolved component output to confirm:
- the final Terraform component and component path
- Terraform workspace name
- backend type and backend settings
- whether a
kind: tfmigratehook already exists - history key and history bucket from
atmos terraform migrate list
Use atmos terraform state show <component> -s <stack> <address> when resource identity or import IDs are unclear.
If a refactor can be handled with Terraform moved blocks and stays in the same state, prefer that unless the user
specifically needs tfmigrate automation or multi-state moves.
One-Off CLI Workflow
Create a migration file in a project-owned migrations directory, then preview it before applying. tfmigrate
resolves --migration relative to the migration_dir in its config. The Atmos-generated default config points
migration_dir at the component's migrations/ directory when one exists. Pass just the filename, not a
migrations/-prefixed path.
atmos terraform migrate plan <component> -s <stack> --migration 20260527090000_refactor_vpc.hcl
atmos terraform migrate apply <component> -s <stack> --migration 20260527090000_refactor_vpc.hcl
What ships with it
1 file 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 · 171 lines · 67 tokens per session scan A a3a0089b3521
atmos-terraform-state-migrations is a skill published in the GitHub repository cloudposse/atmos (1,403 stars, last pushed today), licensed Apache-2.0. It adds 67 tokens to every session and 1,571 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
gke-basics
Trigger: Use when working with Google Kubernetes Engine basics — cluster setup, node pools, workloads, networking, and storage fundamentals.
clum-mcp
A procedure for using clum, a remote Linux operations platform that runs commands through a secure proxy rather than direct SSH. It also describes how to inspect systems, investigate failures, compare solutions, and review incidents.
skypilot-multi-cloud-orchestration
Multi-cloud orchestration for ML workloads with automatic cost optimization. Use when you need to run training or batch jobs across multiple clouds, leverage spot instances with auto-recovery, or optimize GPU costs across providers.
x-nets
Enhanced netstat module with cached data and structured output. View network connections, routing tables, and interface statistics in interactive or TSV/CSV formats. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
x-osv
CLI for Google OSV database. Query vulnerabilities for packages, scan local projects for vulnerable dependencies. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill). Required Tool: Install osv-scanner for project scanning (see https://github.com/google/osv-scanner).
x-uptime
Enhanced uptime with structured YAML output showing uptime, users, and 1/5/15-minute load averages. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.