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-emulatorgit 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-emulator)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-emulator"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-emulator/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-emulator"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-emulator.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.00044 | $0.00746 |
| Opus 5.5 | $0.00018 | $0.00298 |
| Sonnet 5.5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
atmos-emulator 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Emulators
Use this skill for local emulators managed by Atmos. Emulators are stack-scoped, persistent containers that stand in for cloud APIs, Kubernetes, Vault/OpenBao, or OCI registries during local development and testing.
Related Skills
| Need | Load |
|---|---|
| Container component lifecycle | atmos-container |
YAML !emulator references |
atmos-yaml-functions |
| Secrets backed by Vault/OpenBao/SOPS/cloud stores | atmos-secrets |
Workflow emulator and wait steps |
atmos-workflows |
Component Shape
Define emulators under components.emulator:
components:
emulator:
aws:
driver: localstack/aws
region: us-east-1
ephemeral: false
container:
healthcheck:
test: ["CMD", "awslocal", "s3", "ls"]
Supported driver families include AWS, GCP, Azure, Kubernetes (k3s), Vault/OpenBao, and registry
emulators. Check the local docs for exact driver names before generating config for a specific
driver.
Commands
| Command | Purpose |
|---|---|
atmos emulator up <name> -s <stack> |
Start an emulator |
atmos emulator down <name> -s <stack> |
Stop and remove an emulator |
atmos emulator reset <name> -s <stack> |
Stop and wipe persisted state |
atmos emulator ps -s <stack> |
List configured emulators that are running |
atmos emulator list -s <stack> |
List configured emulators and status |
atmos emulator logs <name> -s <stack> |
Show emulator logs |
atmos emulator exec <name> -s <stack> -- <cmd> |
Run a command in the emulator container |
Use --dry-run to preview.
list and ps are configuration-scoped: emulator components declared in the
current Atmos project are the inventory, and the container runtime only supplies
their status. Use --runtime on either command only when diagnosing raw labeled
containers outside the current project configuration. Lifecycle commands prompt
for a stack on an interactive TTY when -s is omitted.
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 · 78 lines · 44 tokens per session scan A 519a57eb93af
atmos-emulator is a skill published in the GitHub repository cloudposse/atmos (1,406 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 746 once invoked, about $0.0002 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.
04-security
A security and operations guide for deploying Dify, an open-source platform for building AI applications, in production.
huawei-cce
Use when creating or managing CCE Kubernetes clusters. Covers cluster creation, node pools, SWR registry, autoscaling. Triggers: CCE, Kubernetes, K8s, cluster, node pool, container, SWR. NOT for: serverless functions (use huawei-functiongraph), serverless containers (use huawei-cce for CCI redirect).
Dokku Docker-Powered Mini-Heroku Self-Hosted PaaS
Dokku is a self-hosted Platform-as-a-Service built on Docker that provides Heroku-like git-push deployment on your own infrastructure. With 32,000+ GitHub stars, it supports buildpacks, Dockerfiles, custom domains, SSL via Let's Encrypt, and a rich plugin ecosystem for databases, caching, and storage.
hatch3r-cli-toolbox
Category-indexed reference for 34 specialist CLI tools beyond the always-on five (ripgrep, jq, gh, fd, fzf). Use to pick the right tool for HTTP clients, ai-chat, structural-search, sed-style edits, data ops, browser automation, container ops, and more.
kubernetes
Skill "kubernetes" from dhaupin/vant, covering kubernetes, when to use, what to do, 1. install kind and 2. create cluster.