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-containergit 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-container)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-container"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-container/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-container"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-container.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.00045 | $0.01472 |
| Opus 5.5 | $0.00018 | $0.00589 |
| Sonnet 5.5 | $0.00009 | $0.00294 |
| Haiku 4.5 | $0.00005 | $0.00147 |
Grade A, and why
atmos-container 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 11d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Container Components
Use this skill for first-class Atmos containers. A container component is a stack-scoped service: one component maps to one container, with image build/push/pull and optional persistent runtime.
Related Skills
| Need | Load |
|---|---|
| Grouping services into systems | atmos-compositions |
Workflow container steps |
atmos-workflows |
| Lifecycle hooks around components | atmos-hooks |
| Local cloud/API emulators | atmos-emulator |
| Secret and env migration | atmos-secrets |
Component Shape
Define containers under components.container in stack manifests.
components:
container:
api:
image: ghcr.io/acme/api:latest
build:
context: services/api
dockerfile: Dockerfile
tags:
- ghcr.io/acme/api:latest
run:
ports:
- host: 8080
container: 8080
command: ./api
env:
LOG_LEVEL: info
composition: app
Container components can participate in hooks, compositions, workflows, and stack-specific config the same way other Atmos component types do.
Relative build.context, build.dockerfile, and run.mounts[].source resolve against the
component's own directory — components.container.base_path (default components/container) joined
with component:/metadata.component, the same mechanism Terraform/Helmfile/Kubernetes/Helm use —
not the directory atmos is invoked from. A component declaring source: is auto-provisioned into a
workdir (same JIT support as other component types), and that workdir becomes the anchor instead.
Commands
| Command | Purpose |
|---|---|
atmos container build <name> -s <stack> |
Build the component image |
atmos container push <name> -s <stack> |
Push the image to its registry |
atmos container pull <name> -s <stack> |
Pull the image |
atmos container run <name> -s <stack> |
Run one foreground container |
atmos container up <name> -s <stack> |
Create/start the persistent container |
atmos container down <name> -s <stack> |
Stop and remove the persistent container |
atmos container ps -s <stack> |
Show running state |
atmos container list -s <stack> |
List container components and state |
atmos container logs <name> -s <stack> |
Show logs |
atmos container exec <name> -s <stack> -- <cmd> |
Execute inside the container |
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.
- 11d ago Changed · +11 lines 857abaf130b4
- 1mo ago First seen · 118 lines · 45 tokens per session scan A 8ae612f0c378
atmos-container is a skill published in the GitHub repository cloudposse/atmos (1,406 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 1,472 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.