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-helmgit 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-helm)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-helm"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-helm/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-helm"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-helm.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.00049 | $0.03186 |
| Opus 5.5 | $0.00020 | $0.01274 |
| Sonnet 5.5 | $0.00010 | $0.00637 |
| Haiku 4.5 | $0.00005 | $0.00319 |
Grade A, and why
atmos-helm 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Native Helm Components
Use this skill for the native Helm component type (components.helm). It deploys Helm charts —
local, remote-repository, or OCI — through the Helm Go SDK, in-process. No helm or helmfile
binary is required. This is a different component type than components.helmfile; see
Native Helm vs. Helmfile below before choosing one.
This feature is experimental.
Related Skills
| Need | Load |
|---|---|
Helmfile-based deployments (shells out to helmfile/helm) |
atmos-helmfile |
| Native Kubernetes manifests/Kustomize (no Helm charts) | atmos-kubernetes |
Component dependency ordering for --all/--affected |
atmos-components |
Secret values in values: (!secret) |
atmos-secrets |
GitOps delivery targets (provision.targets, kind: git) |
atmos-git |
| EKS/cluster authentication | atmos-aws-eks, atmos-auth |
| Native CI job summaries | atmos-ci |
Native Helm vs. Helmfile
Native Helm (components.helm) |
Helmfile (components.helmfile) |
|
|---|---|---|
| Execution | Helm Go SDK, in-process | Shells out to the helmfile and helm binaries |
| Binaries required | None | helmfile, helm (plus any declared helm plugins) |
| Multiple releases per component | One chart/release per component | One or more releases per helmfile.yaml |
| Diff engine | Embedded helm-diff library (no plugin install) |
helmfile diff (needs helm-diff plugin, installed via atmos helm plugin) |
| Values | values:/values_files: merged through Atmos inheritance |
Varfile generated from stack vars: |
| Status | Experimental | Stable |
Use native Helm for straightforward chart deployments where you want no external binaries and
first-class GitOps delivery targets. Use Helmfile (atmos-helmfile)
for existing helmfile.yaml projects, multi-release releases files, or helm-secrets/other Helm CLI
plugins. atmos helm plugin manages plugins for Helmfile components (native Helm does not run Helm
CLI subcommand plugins).
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 Changed · +8 lines af19928f2c60
- 1mo ago Changed · +8 lines c87143b94328
- 1mo ago Changed · +1 lines c3af3d70fcfd
- 1mo ago First seen · 226 lines · 49 tokens per session scan A 9b3ed1f3558c
atmos-helm is a skill published in the GitHub repository cloudposse/atmos (1,403 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 3,186 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.