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-design-patternsgit 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-design-patterns)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-design-patterns"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-design-patterns.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.00025 | $0.02835 |
| Opus 5 | $0.00013 | $0.01418 |
| Sonnet 5 | $0.00005 | $0.00567 |
| Haiku 4.5 | $0.00003 | $0.00283 |
Grade A, and why
atmos-design-patterns 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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Design Patterns
Design patterns are proven solutions for structuring infrastructure configuration in Atmos. They address organizational complexity by providing reusable approaches for multi-account, multi-region, enterprise-grade environments.
Pattern Progression
Most teams follow this growth path:
Inline Configuration (learning/prototyping)
|
Basic Stack Organization (dev/staging/prod)
|
Multi-Region Configuration (add regions)
|
Organizational Hierarchy (add teams/accounts/OUs)
Start with the simplest pattern that meets your needs. You do not need to start with the most complex pattern -- start simple and evolve.
Stack Organization Patterns
Basic Stack Organization
One file per environment. Simplest setup for single-region, single-account-per-stage deployments.
stacks/
catalog/
vpc/
defaults.yaml # Shared component defaults
deploy/
dev.yaml # Imports catalog, sets stage: dev
staging.yaml
prod.yaml
Each environment file imports shared defaults and adds environment-specific overrides:
# stacks/deploy/dev.yaml
import:
- catalog/vpc/defaults
vars:
stage: dev
components:
terraform:
vpc:
vars:
nat_gateway_enabled: false
Deploy with: atmos terraform apply vpc -s dev
Multi-Region Configuration
Extends basic pattern to deploy across multiple AWS regions. Each region gets its own stack file with region-specific settings (CIDR blocks, availability zones).
stacks/deploy/dev/
us-east-2.yaml # region: us-east-2, environment: ue2
us-west-2.yaml # region: us-west-2, environment: uw2
Use name_template: "{{.vars.environment}}-{{.vars.stage}}" in atmos.yaml to generate stack names like ue2-dev.
Organizational Hierarchy Configuration
Enterprise pattern for multiple organizations, OUs/tenants, and accounts. Uses _defaults.yaml files at each hierarchy level to create inheritance chains.
What ships with it
2 files 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 · 411 lines · 25 tokens per session scan A 44d4afc94af5
atmos-design-patterns is a skill published in the GitHub repository cloudposse/atmos (1,372 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 2,835 once invoked, about $0.0001 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
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…
vs-project
Create Viking web projects, start and verify a local preview, or deploy a generated project to Volcengine IGA Pages when explicitly requested. Includes agent-guided feature, eligible application, dataset, scene, and authentication choices. Use only after confirming the installed CLI exposes vs project; otherwise stop…
kastell-ops
Kastell CLI patterns, architecture, anti-patterns, and decision trees. Use automatically when working in Kastell codebase or when asked about Kastell server infrastructure, security audit, hardening, lock, provision, or provider management.
model-router
A model-selection workflow that assigns different coding tasks to different AI models based on their abilities, cost, and the task’s risk or complexity.
cloud-push-quarantine
Inspect and recover rows isolated by cloud push after a server rejection, without exposing row contents. Use when sync-health reports pushquarantine.