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-cachegit 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-cache)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-cache"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-cache/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-cache"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-cache.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.00035 | $0.00741 |
| Opus 5.5 | $0.00014 | $0.00296 |
| Sonnet 5.5 | $0.00007 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
atmos-cache 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Cache
Use this skill for Atmos cache behavior. There are two distinct cache surfaces: CI cache and Terraform registry cache.
Related Skills
| Need | Load |
|---|---|
| Native CI workflows | atmos-ci |
| Tool versions installed into cache roots | atmos-toolchain |
| Terraform component execution | atmos-terraform |
CI Cache
The CI cache restores and saves the Atmos XDG cache root, including toolchain installs and other known cache directories. GitHub Actions is the supported CI provider today.
ci:
cache:
enabled: true
auto: true
paths:
- .terraform
key: atmos-${{ runner.os }}-${{ hashFiles('**/.tool-versions') }}
restore_keys:
- atmos-${{ runner.os }}-
Commands:
| Command | Purpose |
|---|---|
atmos ci cache paths |
Print cache key, paths, and restore keys for actions/cache |
atmos ci cache restore |
Restore the well-known cache directory |
atmos ci cache save |
Save the well-known cache directory |
atmos ci cache list |
List CI cache entries |
atmos ci cache delete <key> |
Delete a CI cache entry |
Use cloudposse/atmos/actions/cache@v1 when the workflow wants a composite action wrapper around
Atmos cache behavior. Otherwise use atmos ci cache paths with actions/cache.
Terraform Registry Cache
atmos terraform cache manages the Atmos Terraform registry cache. It is not Terraform's provider
plugin cache (TF_PLUGIN_CACHE_DIR).
Commands:
| Command | Purpose |
|---|---|
atmos terraform cache list |
List cached providers/modules |
atmos terraform cache mirror |
Pre-seed provider artifacts for multiple platforms |
atmos terraform cache stats |
Show cache size and object counts |
atmos terraform cache prune |
Remove stale metadata |
atmos terraform cache delete <key> |
Delete a cached object |
atmos terraform cache trust |
Trust the cache proxy certificate |
atmos terraform cache untrust |
Remove the trusted certificate |
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 · 82 lines · 35 tokens per session scan A 42c0fd98d2c0
atmos-cache is a skill published in the GitHub repository cloudposse/atmos (1,406 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 741 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
gke-basics
Trigger: Use when working with Google Kubernetes Engine basics — cluster setup, node pools, workloads, networking, and storage fundamentals.
aiox-devops
Activate Gage (devops) for GitHub Repository Manager & DevOps Specialist. Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized to push to remote repository.
aiox-devops
GitHub Repository Manager & DevOps Specialist (Gage). Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized...
managing-railway
Railway platform CLI for service deployment, infrastructure management, and debugging. Use for creating services, managing deployments, configuring networking, and reviewing logs.
github-actions
GitHub Actions CI/CD workflows for automating build, test, and deployment.
security-scanning
CI security scanning: secrets, deps, SAST, triage, expiring exceptions.