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-initnpx skills add cloudposse/atmos --skill atmos-initgit 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-init)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-init"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-init.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.00035 | $0.01214 |
| Opus 5 | $0.00017 | $0.00607 |
| Sonnet 5 | $0.00007 | $0.00243 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
atmos-init 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Init
Use this skill for bootstrapping a brand-new Atmos project from the built-in
template catalog via atmos init.
atmos init is a thin, project-bootstrap-scoped wrapper around the exact same
engine atmos scaffold generate uses (pkg/generator/ui.InitUI). For authoring a
new template — custom fields, conditional when: on fields/files, hooks — load
atmos-scaffold instead; everything documented there (field types, conditional
prompts/files, spec.hooks:, 3-way merge mechanics) applies unchanged to project
templates consumed via init. This skill only covers what's specific to init.
Quick Shape
atmos init basic ./my-project
atmos init aws/landing-zone ./my-project
atmos init # interactive template + target selection
Built-in templates: basic (minimal cloud-agnostic layout), simple, atmos
(atmos.yaml only), aws/app (SDLC repo: dev/staging/prod, native CI, emulator-enabled),
aws/landing-zone, gcp/landing-zone, azure/landing-zone. Run atmos scaffold list
to see all templates, including remote/catalog ones not built in.
atmos init ships experimental — behavior may change between releases.
Shared Template Contract
Every init template is an AtmosScaffoldConfig, so it uses the same contract
as atmos scaffold generate: spec.fields, spec.files, and spec.hooks.
Fields and files can use when: predicates or CEL expressions over earlier
answers; generation hooks run at before.scaffold.generate or
after.scaffold.generate. Scaffold hooks deliberately support only kind: step
and ordered kind: steps, even though stack lifecycle hooks support more kinds.
Load atmos-scaffold before authoring or changing any of those template
features. It contains the field, CEL, file-condition, hook, and template-context
rules that init consumes unchanged.
Differences from atmos scaffold generate
atmos init |
atmos scaffold generate |
|
|---|---|---|
--git default |
true (auto-creates initial commit) | false |
--dry-run |
not available | available |
--defaults |
not available (non-interactive detection only) | available |
list/validate subcommands |
none — use atmos scaffold list/validate |
scaffold list/scaffold validate |
| Template sources | embedded + catalog + direct remote (git/https/s3/oci) | embedded + custom (atmos.yaml) + catalog + direct remote (git/https/s3/oci) |
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 · 105 lines · 35 tokens per session scan A 92b467bb5490
atmos-init is a skill published in the GitHub repository cloudposse/atmos (1,372 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 1,214 once invoked, about $0.0002 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
gws-tasks
Google Tasks: Manage task lists and tasks.
persona-customer-support
Manage customer support — track tickets, respond, escalate issues.
recipe-create-doc-from-template
Copy a Google Docs template, fill in content, and share with collaborators.
recipe-create-events-from-sheet
Read event data from a Google Sheets spreadsheet and create Google Calendar entries for each row.
recipe-create-shared-drive
Create a Google Shared Drive and add members with appropriate roles.
recipe-log-deal-update
Append a deal status update to a Google Sheets sales tracking spreadsheet.