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-project-layoutgit 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-project-layout)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-project-layout"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-project-layout/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-project-layout"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-project-layout.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.00034 | $0.00603 |
| Opus 5.5 | $0.00014 | $0.00241 |
| Sonnet 5.5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
atmos-project-layout 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Project Layout
Use this skill for repository layout, root paths, and how atmos.yaml paths resolve.
Root Paths
base_path sets the root for most relative project paths. Keep it explicit when a repository does
not use the current directory as the Atmos root.
base_path: ""
stacks:
base_path: stacks
components:
terraform:
base_path: components/terraform
workflows:
base_path: stacks/workflows
schemas:
jsonschema:
base_path: stacks/schemas/jsonschema
opa:
base_path: stacks/schemas/opa
Conventional Layout
.
atmos.yaml
atmos.d/
stacks.yaml
components.yaml
auth.yaml
components/
terraform/
helmfile/
packer/
ansible/
stacks/
catalog/
workflows/
orgs/
schemas/
Use atmos.d/ for modular root config when atmos.yaml gets too large. Use stack imports for stack
manifest inheritance and catalog composition; do not confuse root config imports with stack imports.
Path Rules
- Root
base_pathcontrols how project paths resolve. - Subsystem
base_pathvalues are normally relative to the rootbase_path. - Workflow
--filevalues are relative toworkflows.base_path. - Schema paths are relative to their schema base path unless an absolute path is used.
- Stack import paths are a stack-manifest concern; load
atmos-stacksfor stack inheritance details.
Routing
| Need | Load |
|---|---|
Config discovery, merge order, import of root config |
atmos-config |
| Stack discovery, stack imports, stack naming | atmos-stacks |
| Component type directories and component metadata | atmos-components |
| Terraform backend and command-specific path behavior | atmos-terraform |
| Workflow file discovery | atmos-workflows |
| Schema directories and validation paths | atmos-schemas, atmos-validation |
| Profiles path and activation | atmos-profiles |
Guardrails
- Do not force the canonical
components/terraformlayout during migrations; pointbase_pathand component paths at the user's existing repository when that is safer. - Prefer a small root
atmos.yamlplus focusedatmos.d/*.yamlfiles for large projects. - Verify layout assumptions with
atmos describe configbefore generating large changes.
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 · 89 lines · 34 tokens per session scan A b5b935597db8
atmos-project-layout is a skill published in the GitHub repository cloudposse/atmos (1,403 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 603 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.
clum-mcp
A procedure for using clum, a remote Linux operations platform that runs commands through a secure proxy rather than direct SSH. It also describes how to inspect systems, investigate failures, compare solutions, and review incidents.
skypilot-multi-cloud-orchestration
Multi-cloud orchestration for ML workloads with automatic cost optimization. Use when you need to run training or batch jobs across multiple clouds, leverage spot instances with auto-recovery, or optimize GPU costs across providers.
x-nets
Enhanced netstat module with cached data and structured output. View network connections, routing tables, and interface statistics in interactive or TSV/CSV formats. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
x-osv
CLI for Google OSV database. Query vulnerabilities for packages, scan local projects for vulnerable dependencies. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill). Required Tool: Install osv-scanner for project scanning (see https://github.com/google/osv-scanner).
x-uptime
Enhanced uptime with structured YAML output showing uptime, users, and 1/5/15-minute load averages. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.