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-vendoringgit 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-vendoring)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-vendoring"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-vendoring/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-vendoring"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-vendoring.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.00063 | $0.04594 |
| Opus 5.5 | $0.00025 | $0.01838 |
| Sonnet 5.5 | $0.00013 | $0.00919 |
| Haiku 4.5 | $0.00006 | $0.00459 |
Grade A, and why
atmos-vendoring 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 — 480 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Component Vendoring
For scheduled native Component Updater pull requests, scopes/groups, GitHub permissions, and CI summaries, use references/component-updater.md.
Vendoring copies external components, stacks, and other artifacts into your repository. This gives you full control over when and how dependencies change, with visibility through git diff, an immutable audit trail, and the ability to apply emergency patches without waiting for upstream releases.
Atmos records completed installs in the committed vendor.lock.yaml receipt. The receipt contains
credential-free declared and resolved sources, immutable artifact evidence, and the ordered
per-file materialization inventory. It applies to both centralized vendor.yaml sources and
legacy component.yaml sources and mixins.
Why Vendor
Vendoring is the checked-in model for remote component code: you copy the code into the repository, commit it, and control when updates happen. This provides:
- Visibility: See actual code changes via
git diff, not just version bumps. - Audit trail: Every update is a commit with full history for compliance.
- Emergency agility: Patch vulnerabilities immediately without waiting for upstream.
- Developer experience: Full IDE navigation, grep across all code, better onboarding.
- Deployment reliability: No network dependencies during
terraform apply.
Atmos also supports component source provisioning for just-in-time fetching from stack
configuration. Use the atmos-components skill for that model. Prefer vendoring when the fetched
implementation should be reviewed and committed; prefer component source provisioning when the stack
configuration should declare the remote source and Atmos should fetch it on demand.
Types of Vendoring
Atmos supports two approaches:
- Vendor Configuration (
vendor.yaml): A centralized manifest listing all dependencies. This is the recommended approach. - Component Manifest (
component.yaml): A per-component manifest placed inside the component directory. This is the legacy approach.
What ships with it
3 files 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 · 480 lines · 63 tokens per session scan A 2dda28aadc98
atmos-vendoring is a skill published in the GitHub repository cloudposse/atmos (1,407 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 4,594 once invoked, about $0.0003 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.
repo
Convention + tooling for where agent-cloned repos live and how their worktrees are arranged. Default bare repo at /.x-repo/.bare/ / / .git with linked working trees under /.x-repo/ / / [/@ ]. Discovered via x repo ls. Worktree management via x repo wt. Use for "where to clone", "git clone path", "workspace layout"…
gh
You have access to gh (GitHub CLI) for repository and project management.