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-settingsgit 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-settings)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-settings"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-settings/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-settings"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-settings.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.00038 | $0.01025 |
| Opus 5.5 | $0.00015 | $0.00410 |
| Sonnet 5.5 | $0.00008 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
atmos-settings 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Settings
Use this skill for global atmos.yaml options that are not owned by a narrower subsystem skill.
Owned Sections
| Section | Use for |
|---|---|
settings |
Global CLI behavior, terminal behavior, telemetry, experimental options |
logs |
Log level, log file path, log color, debug output behavior |
errors |
Error output formatting and error reporting options |
env |
Environment variables applied to Atmos operations |
docs |
Documentation generation defaults |
metadata |
Project-level metadata such as name, tags, and version |
version |
Minimum or maximum Atmos version constraints |
If a setting belongs to a subsystem such as templates, validation, auth, CI, or toolchain, load that subsystem skill instead.
Common Pattern
settings:
terminal:
pager: false
syntax_highlighting:
enabled: true
telemetry:
enabled: false
logs:
level: Info
env:
AWS_REGION: us-east-1
metadata:
name: platform-infrastructure
Terminal Appearance and Color
settings.terminal controls Atmos's terminal output appearance (color, theme, width, unicode,
syntax highlighting, pager). Fields:
settings:
terminal:
color: true # Explicitly force color on (overrides TTY auto-detection)
no_color: false # Deprecated: use the --no-color flag or ATMOS_NO_COLOR/NO_COLOR env vars instead
force_color: false # ENV-only (ATMOS_FORCE_COLOR) -- not settable from this config field
theme: dracula # Theme name; see `atmos theme list` for available names
max_width: 120
unicode: true
syntax_highlighting:
enabled: true
pager: false # false/true/off/on/"less"/a specific pager command
Precedence: no_color (config) is deprecated in favor of the --no-color flag/env vars below.
IsColorEnabled logic: no_color forces color off; else explicit color: true forces it on;
otherwise Atmos falls back to TTY auto-detection.
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 Changed · +3 lines 67dbebc278bb
- 1mo ago Changed 8852ef97a4ef
- 1mo ago First seen · 113 lines · 38 tokens per session scan A 718ebeb21b8f
atmos-settings is a skill published in the GitHub repository cloudposse/atmos (1,403 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 1,025 once invoked, about $0.0002 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.