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-modernizationgit 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-modernization)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-modernization"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-modernization/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-modernization"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-modernization.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.00036 | $0.02420 |
| Opus 5.5 | $0.00014 | $0.00968 |
| Sonnet 5.5 | $0.00007 | $0.00484 |
| Haiku 4.5 | $0.00004 | $0.00242 |
Grade A, and why
atmos-modernization 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 yesterday.
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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Modernization
Use this skill when updating older Atmos projects to current conventions. "Atmos Modernization" is the umbrella term for replacing legacy patterns with supported, current patterns.
Modernization Checklist
| Legacy pattern | Replace with |
|---|---|
name_pattern |
name_template or explicit stack name |
settings.depends_on |
dependencies.components |
Custom command type: component/type: stack on arguments, or semantic_type: component/semantic_type: stack on flags |
provides: component/provides: stack on both arguments and flags |
cloudposse/github-action-atmos* wrapper actions |
Native CI with direct atmos commands |
cloudposse/github-action-atmos-component-updater |
atmos vendor update --pull-request with native GitHub PR publishing |
cloudposse/github-action-setup-atmos as default |
GitHub Actions container ghcr.io/cloudposse/atmos:<version> |
apt-get install docker.io in an Atmos container job |
Remove it: the official Atmos image already ships with docker.io |
GitHub Actions concurrency around jobs or workflows that invoke atmos |
An explicit promotion workflow or deployment controller — environments and merge queues are approval/merge-order controls, not deployment-order guarantees; a concurrency group evicts its pending run regardless of cancel-in-progress |
hashicorp/setup-terraform / opentofu/setup-opentofu in Atmos jobs |
Atmos dependencies.tools and toolchain |
Manual atmos toolchain install <tool> preinstall steps for Atmos-owned tools |
Declarative dependencies.tools at the owning component, workflow, hook, or custom command |
Large inline workflow/custom-command shell scripts, repeated echo, shell loops, ad hoc sleeps |
Native step types such as atmos, toast, table, parallel, matrix, wait, container, emulator, and http |
| Hand-rolled scheduled drift GitHub Actions | Atmos Pro drift detection |
cloudposse/github-action-atmos-terraform-drift-* |
settings.pro.drift_detection plus atmos terraform plan --upload-status |
| Secret values through raw store calls | Declared secrets.vars plus !secret |
| Legacy hook event spelling | Modern dotted lifecycle events such as after.terraform.plan |
| Static GitHub tokens in URLs | Atmos Auth github/sts through Atmos Pro |
cloudposse/terraform-aws-components sources |
Repos in the cloudposse-terraform-components organization |
Parser-specific doubled double quotes ("") in !terraform.state or !terraform.output expressions |
Direct YQ expressions; quote only as required by YAML |
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.
- yesterday Changed · +45 lines ea337cf39803
- 1mo ago First seen · 168 lines · 36 tokens per session scan A cbb6dbdcd2f7
atmos-modernization is a skill published in the GitHub repository cloudposse/atmos (1,405 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 2,420 once invoked, about $0.0001 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
devloop
Goal-driven development loop — define objective, write rules with key-results, verify visually, sync to issue tracker.
assess
Multi-phase project assessment with scoring. Triggered by "/assess" to evaluate project health across dimensions and generate a comprehensive report.
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
goal
Set and track project goals. Triggered by "/goal" to define objectives, track milestones, or review progress.
gke-basics
Trigger: Use when working with Google Kubernetes Engine basics — cluster setup, node pools, workloads, networking, and storage fundamentals.
squads-cli
Squads CLI — operate your squads through the loop; intent in, reviewed work out. TRIGGER when running squads, dispatching agents, triaging the inbox, reading/writing memory, recording feedback, or checking status/usage.