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-profilesnpx skills add cloudposse/atmos --skill atmos-profilesgit 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-profiles)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-profiles"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-profiles.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 | $0.00035 | $0.00591 |
| Opus 5 | $0.00017 | $0.00296 |
| Sonnet 5 | $0.00007 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
atmos-profiles 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 yesterday.
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Profiles
Use this skill when configuring or troubleshooting Atmos profiles: named configuration overlays
selected with --profile or ATMOS_PROFILE.
Purpose
Profiles let teams switch configuration contexts without changing the base project config. Use them for developer, CI, tenant, cloud account, or environment-specific overrides.
atmos --profile developer terraform plan vpc -s dev
ATMOS_PROFILE=ci atmos terraform deploy vpc -s prod
Use --profile with no value in an interactive terminal to open a multi-select picker of every
discovered profile. Non-interactive contexts (CI, scripts) must pass --profile=<name> or
ATMOS_PROFILE explicitly.
Profile Layout
Keep profile files focused and aligned with the sections they override:
profiles/
developer/
atmos.yaml
auth.yaml
ci/
atmos.yaml
auth.yaml
Profile configuration is merged into the active Atmos configuration. Put shared defaults in the base config, then keep each profile to the smallest override needed.
Profile Config
Configure the profile search location in root config when the default location is not sufficient:
profiles:
base_path: profiles
Example profiles/ci/auth.yaml override:
auth:
providers:
github-oidc:
kind: github/oidc
region: us-east-1
identities:
deploy:
kind: aws/assume-role
via:
provider: github-oidc
Routing
| Need | Load |
|---|---|
| Profile activation, directory layout, merge behavior | stay in atmos-profiles |
| Auth providers, identities, OIDC, SSO, keyring in profiles | atmos-auth |
CI use of ATMOS_PROFILE |
atmos-ci |
| Tool versions or registries that differ by profile | atmos-toolchain |
| Base paths and profile-relative file layout | atmos-project-layout |
Guardrails
- Keep profile overrides small and predictable; avoid duplicating the whole base
atmos.yaml. - Use the same provider and identity names across profiles when callers should not care which profile is active.
- Prefer
ATMOS_PROFILEin CI and--profilefor one-off local commands. - Verify the active merged configuration with
atmos describe configor the relevantatmos describe componentcommand.
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.
- yesterday First seen · 88 lines · 35 tokens per session scan A 6ed5e2237fd0
atmos-profiles 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 591 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
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
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.
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…
hunt-cicd
Hunt CI/CD pipeline vulnerabilities — GitHub Actions workflow injection (pullrequesttarget Pwnrequest + ${{ }}-into-shell), self-hosted runner poisoning, OIDC trust-policy abuse, Jenkins script-console RCE and CVE-2024-23897 file read, GitLab CI runner-token registration, Terraform state file leakage, artifact/log…
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
cicd-secrets-exfil
Extracting CI secrets / OIDC tokens once you have code execution in a build job — echo/printenv exfil, log-masking bypass (base64, char-split, reversal), OIDC token abuse to assume cloud roles, GITHUBTOKEN / CIJOBTOKEN scope abuse, cache / artifact secret leakage, provenance pivot.