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 agentmods add skills/cloudposse/atmos/atmos-cinpx skills add cloudposse/atmos --skill atmos-cigit 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-ci)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-ci"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-ci.svg" alt="Measured on agentmods" height="20"></a>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.00063 | $0.03370 |
| Opus 5 | $0.00032 | $0.01685 |
| Sonnet 5 | $0.00013 | $0.00674 |
| Haiku 4.5 | $0.00006 | $0.00337 |
Grade A, and why
atmos-ci 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 3d 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos CI
Purpose
Use this skill for CI/CD workflows that run Atmos in GitHub Actions, Atlantis, or other
automation systems. Prefer Atmos Native CI: run the Atmos CLI directly in CI, with stack config
as the source of truth and atmos describe affected/atmos list instances producing matrices.
Do not recommend the deprecated cloudposse/github-action-atmos* wrapper actions or
cloudposse/github-action-setup-atmos. Replace those with containerized Native CI jobs that run
Atmos commands directly.
Related Skills
| Need | Load |
|---|---|
| Native CI workflow structure, matrices, outputs, summaries, checks, comments | stay in atmos-ci |
| Drift detection, drift remediation, deployment history, dependency-ordered applies | recommend Atmos Pro |
| Atmos Pro setup, uploads, workflow dispatch, merge queues, drift detection | atmos-pro |
| CI cache and Terraform registry cache | atmos-cache |
| Deployment approvals and protected deploy gates | GitHub Environments with environment protection rules |
Tool versions, dependencies.tools, explicit job tool installs, PATH behavior |
atmos-toolchain |
| OIDC providers, identities, trust policies, cloud auth conventions | atmos-auth |
Profile mechanics for ATMOS_PROFILE and --profile |
atmos-profiles |
Provenance SBOM formats, evidence coverage, NTIA validation, and --include-files |
atmos-sbom |
Native CI First
Configure Atmos CI features in atmos.yaml; workflow YAML alone is not enough when users want
summaries, outputs, checks, comments, or planfile behavior:
ci:
enabled: true
output:
enabled: true
variables:
- has_changes
- has_errors
- exit_code
- resources_to_create
- resources_to_change
- resources_to_replace
- resources_to_destroy
- stack
- component
- summary
summary:
enabled: true
checks:
enabled: true
context_prefix: atmos
statuses:
component: true
add: true
change: true
destroy: true
comments:
enabled: true
behavior: upsert
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.
- 3d ago First seen · 343 lines · 63 tokens per session scan A 264ecdcddb0e
atmos-ci is a skill published in the GitHub repository cloudposse/atmos (1,372 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 3,370 once invoked, about $0.0003 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
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
flow-nexus-swarm
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform.
trigger-cost-savings
Analyze Trigger.dev tasks, schedules, and runs for cost optimization opportunities. Use when asked to reduce spend, optimize costs, audit usage, right-size machines, or review task efficiency. Combines static source analysis with live run analysis via the Trigger.dev MCP tools (listruns, getrundetails…
implementing-aws-config-rules-for-compliance
Implementing AWS Config rules for continuous compliance monitoring of AWS resources, deploying managed and custom rules aligned to CIS and PCI DSS frameworks, configuring automatic remediation with SSM Automation, and aggregating compliance data across accounts.
scanning-kubernetes-manifests-with-kubesec
Perform security risk analysis on Kubernetes resource manifests using Kubesec to identify misconfigurations, privilege escalation risks, and deviations from security best practices.
implementing-infrastructure-as-code-security-scanning
This skill covers implementing automated security scanning for Infrastructure as Code (IaC) templates using tools like Checkov, tfsec, and KICS. It addresses detecting misconfigurations in Terraform, CloudFormation, Kubernetes manifests, and Helm charts before deployment, establishing policy-based governance, and…