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-ansiblegit 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-ansible)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-ansible"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-ansible/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-ansible"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-ansible.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.00027 | $0.03359 |
| Opus 5 | $0.00014 | $0.01680 |
| Sonnet 5 | $0.00005 | $0.00672 |
| Haiku 4.5 | $0.00003 | $0.00336 |
Grade A, and why
atmos-ansible 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 9d 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 — 471 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Ansible Orchestration
Atmos wraps the Ansible CLI to provide stack-aware orchestration of configuration management operations. Instead of manually managing variables, inventory, and playbook paths for each Ansible component, Atmos resolves the full configuration from stack manifests and handles all of these concerns automatically.
Note:
atmos ansible playbookis designed for interactive operator sessions where a human is present to monitor output, respond to prompts, and approve changes. It is not suitable for headless CI/CD automation where no interactive terminal is available. For automated pipelines, use a dedicated Ansible CI runner or invokeansible-playbookdirectly from a CI step with pre-exported credentials.
How Atmos Orchestrates Ansible
When you run atmos ansible playbook, Atmos performs the following sequence:
- Resolves stack configuration -- Reads and deep-merges all stack manifests to produce the fully resolved configuration for the target component in the target stack.
- Generates a variables file -- Writes a YAML file containing all
varsdefined for the component in the stack, following the naming convention<context>-<component>.ansible.vars.yaml. - Resolves the playbook -- Determines the playbook to run from
--playbookflag orsettings.ansible.playbookin the stack manifest. - Resolves the inventory -- Determines the inventory source from
--inventoryflag orsettings.ansible.inventoryin the stack manifest. - Sets environment variables -- Applies all
envsettings from the stack manifest. - Executes
ansible-playbook-- Runs the playbook in the component directory, passing the generated variables file via--extra-vars @<varfile>and any additional native flags. - Cleans up -- Removes the generated variables file after execution completes.
This means a single command like atmos ansible playbook webserver -s prod replaces what would normally require
finding the right playbook, constructing extra-vars, specifying inventory, and managing environment variables
manually.
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.
- 9d ago First seen · 471 lines · 27 tokens per session scan A 5a3cb949db8d
atmos-ansible is a skill published in the GitHub repository cloudposse/atmos (1,372 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 3,359 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
trigger-cost-savings
Analyze Trigger.dev tasks, schedules, and runs for cost optimization opportunities. Use when asked to reduce spend, optimize costs, audit usage, right-size machines, or review task efficiency. Combines static source analysis with live run analysis via the Trigger.dev MCP tools (listruns, getrundetails…
vs-project
Create Viking web projects, start and verify a local preview, or deploy a generated project to Volcengine IGA Pages when explicitly requested. Includes agent-guided feature, eligible application, dataset, scene, and authentication choices. Use only after confirming the installed CLI exposes vs project; otherwise stop…
kastell-ops
Kastell CLI patterns, architecture, anti-patterns, and decision trees. Use automatically when working in Kastell codebase or when asked about Kastell server infrastructure, security audit, hardening, lock, provision, or provider management.
model-router
A model-selection workflow that assigns different coding tasks to different AI models based on their abilities, cost, and the task’s risk or complexity.
cloud-push-quarantine
Inspect and recover rows isolated by cloud push after a server rejection, without exposing row contents. Use when sync-health reports pushquarantine.
new-gh-issue-orchestration
Orchestrates a GitHub-issue-driven delivery workflow from issue intake to PR creation using reviewer-first then worker execution. Invoked when the user provides a GitHub issue link/number and asks to start end-to-end delivery.