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-stepsgit 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-steps)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-steps"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-steps/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-steps"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-steps.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.00039 | $0.03099 |
| Opus 5.5 | $0.00016 | $0.01240 |
| Sonnet 5.5 | $0.00008 | $0.00620 |
| Haiku 4.5 | $0.00004 | $0.00310 |
Grade C, and why
atmos-steps scanned grade C with 1 finding 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Use `type: workdir` with `source` and `reset` instead of `mkdir`, `rm -rf`, How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Steps
Atmos steps are the shared execution DSL used by workflows, custom commands,
hooks (kind: step), and cast recordings. When a task involves steps:, step
type, working_directory, env, output, retries, or hook with: payloads,
use this skill together with the surface-specific skill (atmos-workflows,
atmos-custom-commands, or atmos-hooks).
For interpreter: starlark, also load atmos-starlark for the embedded API,
parallel functions, immutable inputs, and module loading.
Core Model
A step is a typed action with native fields. Do not treat steps as a place to write shell scripts by default. Prefer the Atmos field that expresses the operation directly:
- Use
working_directoryinstead ofcdfor real execution. Atype: simulatechild of amode: stepscast may displaycd <directory>to narrate a directory transition, but it never changes the working directory of later real steps. - Use
envmaps instead of inlineFOO=bar commandorexport. - Use
output: noneinstead of redirecting to/dev/null. - Use
type: scriptinstead of heredoc shell snippets likepython3 - <<'PY'. - Use
type: workdirwithsourceandresetinstead ofmkdir,rm -rf, andcp. - Use
type: atmosfor Atmos commands instead of shelling out toatmos ...when the surface supports typed steps. - Use Atmos Terraform/OpenTofu
rcconfiguration instead of hand-managing temporary.terraformrcor.tofurcfiles.
Shell is still valid for real shell work, but it should be a conscious fallback when no native step type or field expresses the intent.
Where Steps Run
Step fields are shared, but defaults differ by surface:
- Workflows default command steps to
type: atmos. - Custom command string steps historically behave like shell commands; use structured step objects when you need typed behavior.
- Hooks use an envelope plus
with:. Forkind: step, the hook'stypeselects the step type, whilewith:contains the step-specific fields. - Cast steps can run nested steps and record their terminal output.
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.
- 2d ago Changed · +33 lines c852a695c1d2
- 1mo ago Changed 1a88591b4a2e
- 1mo ago Changed · +3 lines 36ea9b11f8d3
- 1mo ago First seen · 240 lines · 39 tokens per session scan C 6db02062b02f
atmos-steps is a skill published in the GitHub repository cloudposse/atmos (1,403 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 3,099 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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.