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-importsgit 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-imports)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-imports"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-imports/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-imports"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-imports.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.00044 | $0.00897 |
| Opus 5 | $0.00022 | $0.00449 |
| Sonnet 5 | $0.00009 | $0.00179 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
atmos-imports 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 5d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Imports
Use this skill for stack manifest import: behavior, especially remote imports. Imports pull
stack configuration, not component source code.
Related Skills
| Need | Load |
|---|---|
| General stack structure and merge precedence | atmos-stacks |
| Component source provisioning and vendoring | atmos-vendoring |
| Private GitHub auth with Atmos Pro STS | atmos-auth |
| Migration from old import/name patterns | atmos-modernization |
Import Basics
import:
- catalog/vpc/defaults
- mixins/region/us-east-2
- orgs/acme/plat/prod/_defaults
Atmos resolves imports before producing the final stack. Use imports for _defaults.yaml, mixins,
catalog defaults, reusable stack fragments, and remote stack configuration.
If both file.yaml and file.yaml.tmpl exist, the template version is preferred. Template imports
can receive context and render before merge.
Remote Imports
Remote imports use the same stack import: key:
import:
- https://raw.githubusercontent.com/acme/config/main/stacks/catalog/vpc.yaml
- github://acme/config/main/stacks/catalog/eks.yaml
- git::https://github.com/acme/config.git//stacks/catalog/db.yaml?ref=v1.2.3
- s3::https://s3.amazonaws.com/acme-configs/stacks/catalog/vpc.yaml
- gcs::gs://acme-configs/stacks/catalog/eks.yaml
- oci://ghcr.io/acme/atmos-config:v1.2.3
Use pinned refs or immutable artifact tags for production imports. Prefer HTTPS/GitHub forms for read-only public config and Git/OCI forms when versioning, auth, or packaged artifacts matter.
Import vs Source vs Vendoring
import:pulls stack YAML configuration.- Component
source:provisions component source code. vendor.yamlplusatmos vendor pullmaterializes external files into the repository.
Remote imports do not create components/terraform/<name> directories. If a remote imported stack
references a component whose source is not local, also configure component source: or vendor the
component with atmos vendor pull.
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.
- 5d ago First seen · 104 lines · 44 tokens per session scan A cad6dcfeba67
atmos-imports is a skill published in the GitHub repository cloudposse/atmos (1,372 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 897 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
persona-customer-support
Manage customer support — track tickets, respond, escalate issues.
recipe-create-doc-from-template
Copy a Google Docs template, fill in content, and share with collaborators.
recipe-create-events-from-sheet
Read event data from a Google Sheets spreadsheet and create Google Calendar entries for each row.
recipe-create-shared-drive
Create a Google Shared Drive and add members with appropriate roles.
recipe-log-deal-update
Append a deal status update to a Google Sheets sales tracking spreadsheet.
recipe-post-mortem-setup
Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.