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-yaml-functionsgit 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-yaml-functions)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-yaml-functions"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-yaml-functions/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-yaml-functions"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-yaml-functions.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.00073 | $0.03678 |
| Opus 5.5 | $0.00029 | $0.01471 |
| Sonnet 5.5 | $0.00015 | $0.00736 |
| Haiku 4.5 | $0.00007 | $0.00368 |
Grade A, and why
atmos-yaml-functions 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 2d 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos YAML Functions
Overview
YAML functions are the recommended way to add dynamic behavior to Atmos stack configurations.
They use YAML explicit tags (the ! prefix) and operate on structured data after YAML parsing.
They cannot break YAML syntax, are type-safe, and produce clear error messages.
All YAML functions support Go template expressions in their arguments. Atmos processes templates first, then executes the YAML functions.
Available YAML Functions
| Function | Purpose |
|---|---|
!terraform.state |
Read Terraform outputs directly from state backend (fastest, recommended) |
!terraform.output |
Read Terraform outputs via terraform output (requires init, slower) |
!store |
Read values from stores using component/stack/key pattern |
!store.get |
Read arbitrary keys from stores (no naming convention required) |
!secret |
Resolve declared secrets from configured secret backends |
!emulator |
Resolve local emulator connection details |
!labels |
Read all metadata labels, or !labels key [default] for one string value |
!tags / !labels.keys / !labels.values |
Read metadata tags, sorted label keys, or values ordered by key |
!env |
Read environment variables (from stack env: sections or OS) |
!exec |
Execute shell scripts and use the output |
!include |
Include local or remote files (YAML, JSON, HCL, text) |
!include.raw |
Include files as raw text regardless of extension |
!template |
Evaluate Go template expressions and convert JSON to YAML types |
!append |
Append values to inherited lists without replacing the whole list |
!unset |
Remove inherited keys or values from merged config |
!literal |
Preserve values verbatim, bypassing all template processing |
!starlark |
Compute typed values with Starlark from the component's merged config (ctx); stack manifests only |
!random |
Generate cryptographically secure random integers |
!cwd |
Get the current working directory |
!repo-root |
Get the repository root directory |
!aws.account_id |
Get the current AWS account ID via STS |
!aws.caller_identity_arn |
Get the current AWS caller identity ARN |
!aws.caller_identity_user_id |
Get the AWS caller identity user ID |
!aws.organization_id |
Get the current AWS Organization ID |
!aws.region |
Get the current AWS region from SDK config |
!git.host |
Get the current repository host |
!git.name |
Get the current repository name |
!git.owner |
Get the current repository owner |
!git.repository |
Get the owner/repository slug |
!git.url |
Get the repository URL |
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.
- 2d ago Changed · +1 lines · +5 tokens per session 69769a89de78
- 12d ago Changed · +24 lines 8094a53ea39c
- 1mo ago Changed · +2 lines 62134154518a
- 1mo ago Changed · +29 lines 3046fedfea93
- 1mo ago First seen · 309 lines · 68 tokens per session scan A 8672bdce79b4
atmos-yaml-functions is a skill published in the GitHub repository cloudposse/atmos (1,403 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 3,678 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
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.