What is atmos-profiles?

A guide to Atmos profiles, which are named configuration overlays selected for a developer, CI job, tenant, cloud account, or environment. A profile changes selected settings while keeping the shared base configuration.

Use it to define profile directories, activate profiles from the command line or environment, and override authentication, toolchain, and other configuration per context.

It makes it possible to switch contexts without editing the main project configuration or maintaining separate copies of it.

atmos-profiles — Skill for Claude Code by cloudposse/atmos

About the project

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.

cloudposse/atmos · 1,405 stars · on GitHub · atmos.tools

Install

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.

Any agent

npx skills add cloudposse/atmos --skill atmos-profiles

Clone the repo

git clone --depth 1 https://github.com/cloudposse/atmos

Made for: Claude Code.

Or install atmos, the plugin that ships this one along with the rest of its 55 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-profiles/github.svg)](https://agentmods.dev/skills/cloudposse/atmos/atmos-profiles)

Your own site

<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-profiles"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-profiles/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-profiles"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-profiles.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 591 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00591
Opus 5.5	$0.00014	$0.00236
Sonnet 5.5	$0.00007	$0.00118
Haiku 4.5	$0.00003	$0.00059

Measured 1mo ago against content hash 6ed5e2237fd0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

agent-skills/skills/atmos-profiles/SKILL.md · 88 lines

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_PROFILE in CI and --profile for one-off local commands.
Verify the active merged configuration with atmos describe config or the relevant atmos describe component command.

Read the full file on GitHub · 88 lines

Changes

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.

1mo ago First seen · 88 lines · 35 tokens per session scan A 6ed5e2237fd0

Subscribe to this mod's changes

atmos-profiles is a skill published in the GitHub repository cloudposse/atmos (1,405 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 591 once invoked, about $0.0001 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.

CI and CD Cloud DevOps and cloud Orchestration automation cli hcl2

atmos-profiles

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Atmos Profiles

Purpose

Profile Layout

Profile Config

Routing

Guardrails

What this file has done since we first saw it

Other skills, from other repositories

gke-basics

aiox-devops

aiox-devops

managing-railway

github-actions

security-scanning