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-hooksgit 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-hooks)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-hooks"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-hooks/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-hooks"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-hooks.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.00046 | $0.02541 |
| Opus 5.5 | $0.00018 | $0.01016 |
| Sonnet 5.5 | $0.00009 | $0.00508 |
| Haiku 4.5 | $0.00005 | $0.00254 |
Grade A, and why
atmos-hooks 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Hooks
Use this skill for lifecycle hooks that run before or after component operations, or for generation hooks declared in a scaffold template.
Hooks can run scanners, policy checks, store writes, Git actions, custom commands, or other toolchain-aware automation around Terraform, Helm, Kubernetes, and other component commands.
Related Skills
| Need | Load |
|---|---|
| Store output hooks | atmos-stores |
Shared step fields and kind: step payloads |
atmos-steps |
| Post-deployment smoke tests and integration checks | atmos-tests |
| Git hooks and GitOps repositories | atmos-git |
| Tool installation for hook commands | atmos-toolchain |
| TFLint hooks, standalone linting, and rule configuration | atmos-lint |
| CI summaries and Atmos Pro upload | atmos-ci and atmos-pro |
Hook Shape
Hooks are configured in stack manifests at global, component-type, or component scope.
hooks:
store-vpc-outputs:
events:
- after.terraform.apply
kind: store
name: prod/ssm
outputs:
vpc_id: .vpc_id
components:
terraform:
vpc:
hooks:
scan-plan:
events:
- after.terraform.plan
kind: trivy
Modern dotted event names such as after.terraform.plan are preferred. Legacy hyphenated event
names may appear in older stacks; modernize them when editing nearby config.
Lifecycle Events
Use before/after events for component operations, for example:
before.terraform.init,after.terraform.initbefore.terraform.plan,after.terraform.planbefore.terraform.apply,after.terraform.applybefore.terraform.deploy,after.terraform.deploybefore.terraform.test,after.terraform.testbefore.terraform.output,after.terraform.output— fires foratmos terraform output, useful for backfilling a store from already-deployed infrastructure without anapplybefore.terraform.refresh,after.terraform.refresh
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 · +16 lines 602cdbf79548
- 17d ago Changed · +1 lines e08f495b78ce
- 25d ago Changed · +10 lines dafd8783799a
- 1mo ago Changed · +2 lines 3c568b80a5c5
- 1mo ago First seen · 192 lines · 46 tokens per session scan A 3045de89a581
atmos-hooks is a skill published in the GitHub repository cloudposse/atmos (1,405 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 2,541 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
aiox-devops
Activate Gage (devops) for GitHub Repository Manager & DevOps Specialist. Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized to push to remote repository.
aiox-devops
GitHub Repository Manager & DevOps Specialist (Gage). Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized...
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
csv
CSV data processing — view, filter, convert, merge tabular data. Zero barrier — use with x-cmd, Python, or awk. Use for "csv", "data", "table", "spreadsheet", "conversion".
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.