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-progit 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-pro)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-pro"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-pro/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-pro"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-pro.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.00038 | $0.01166 |
| Opus 5.5 | $0.00015 | $0.00466 |
| Sonnet 5.5 | $0.00008 | $0.00233 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
atmos-pro 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Pro
Use this skill when configuring or debugging Atmos Pro, including CI uploads, workflow dispatch, stack locking, GitHub App commits, merge queues, and drift detection.
Atmos Pro is the control plane for visibility and coordination. Atmos CLI remains the execution layer for plans, applies, deploys, auth, toolchains, and stack resolution.
Related Skills
| Need | Load |
|---|---|
| GitHub Actions job structure and Native CI | atmos-ci |
atmos/pro provider and github/sts integration |
atmos-auth |
| Managed Git repositories and signed/pushed commits | atmos-git |
| Migrating old drift/action patterns | atmos-modernization |
Minimal Setup
Configure the workspace ID in atmos.yaml or ATMOS_PRO_WORKSPACE_ID. It is not a secret.
settings:
pro:
workspace_id: "your-workspace-id"
In GitHub Actions, grant OIDC permission. Do not use static API keys for normal GitHub Actions workflows.
permissions:
id-token: write
contents: read
Atmos Pro exchanges the GitHub Actions OIDC token for a short-lived bearer token. The OIDC request URL/token are normally supplied by GitHub automatically.
Core Commands
| Command | Purpose |
|---|---|
atmos describe affected --upload |
Upload affected stacks/components for PR and merge-queue correlation |
atmos list instances --upload |
Upload full component instance inventory |
atmos terraform plan <component> -s <stack> --upload-status |
Upload raw plan status for drift detection |
atmos pro lock --component <component> --stack <stack> |
Lock a stack/component before mutation |
atmos pro unlock --component <component> --stack <stack> |
Release a stack/component lock |
atmos pro commit -m "<message>" --all |
Commit CI-generated changes through the Atmos Pro GitHub App |
atmos pro commit is for workflows that need committed changes to trigger follow-on CI. Commits
created with GITHUB_TOKEN do not trigger subsequent GitHub Actions workflows; commits created by
the Atmos Pro GitHub App do.
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 · 141 lines · 38 tokens per session scan A 07c96a6a651a
atmos-pro is a skill published in the GitHub repository cloudposse/atmos (1,405 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 1,166 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
csv
CSV data processing — view, filter, convert, merge tabular data. Zero barrier — use with x-cmd, Python, or awk. Use for "csv", "data", "table", "spreadsheet", "conversion".
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
gke-basics
Trigger: Use when working with Google Kubernetes Engine basics — cluster setup, node pools, workloads, networking, and storage fundamentals.
glab
GitLab CLI for managing issues, merge requests, CI/CD pipelines, and repositories. Use when: (1) Creating, reviewing, or merging MRs, (2) Managing GitLab issues, (3) Monitoring or triggering CI/CD pipelines, (4) Working with self-hosted GitLab instances, (5) Automating GitLab workflows from the command line. Requires…
gh-infra
Overview of gh-infra and command workflow (import, validate, plan, apply). Use when managing GitHub repository settings, labels, actions settings, rulesets, secrets, variables, or files declaratively via YAML manifests.