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-devcontainergit 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-devcontainer)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-devcontainer"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-devcontainer/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-devcontainer"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-devcontainer.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.00031 | $0.01471 |
| Opus 5.5 | $0.00012 | $0.00588 |
| Sonnet 5.5 | $0.00006 | $0.00294 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
atmos-devcontainer 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Devcontainer
Purpose
Atmos provides native devcontainer management for creating standardized, reproducible development environments. It provides built-in orchestration that integrates with Atmos authentication, toolchains, and project configuration, replacing the need for external orchestration tooling like Geodesic (though Geodesic container images remain fully supported).
Note: The devcontainer feature is currently experimental. By default (settings.experimental: warn),
Atmos displays a warning but runs the command. Set settings.experimental: silence in atmos.yaml to
suppress the warning, or disable to block experimental commands entirely.
Core Concepts
Devcontainer Configuration
Devcontainers are configured at the top level of atmos.yaml (not under components:).
Each named devcontainer defines container settings and a devcontainer spec:
devcontainer:
default:
settings:
runtime: docker # docker or podman (auto-detected if omitted)
spec:
name: "Atmos Default"
image: "cloudposse/geodesic:latest"
workspaceFolder: "/workspace"
workspaceMount: "type=bind,source=${WORKSPACE},target=/workspace"
mounts:
- "type=bind,source=${HOME}/.aws,target=/root/.aws,readonly"
forwardPorts:
- 8080
containerEnv:
ATMOS_BASE_PATH: "/workspace"
remoteUser: "root"
Supported Spec Features
The following devcontainer spec fields are supported:
| Field | Description |
|---|---|
name |
Display name for the container |
image |
Container image to use |
build.dockerfile |
Path to Dockerfile |
build.context |
Build context directory |
build.args |
Build arguments |
workspaceFolder |
Path inside container for workspace |
workspaceMount |
Mount specification for workspace |
mounts |
Additional mount points |
forwardPorts |
Ports to forward to host |
portsAttributes |
Port binding configuration |
runArgs |
Extra arguments passed to container runtime |
containerEnv |
Environment variables set inside container |
remoteUser |
User to run as inside container |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 229 lines · 31 tokens per session scan A 04fe9ebbf481
atmos-devcontainer is a skill published in the GitHub repository cloudposse/atmos (1,407 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 1,471 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.
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.
strut
Operate and manage Docker Compose stacks on VPS infrastructure with the strut CLI. Use for any strut task — deploying and releasing services, database backup and restore, debugging production issues, detecting config drift, rotating secrets and keys, setting up monitoring, configuring domains and SSL, validating…