Agent skill

Atmos Modernization

by cloudposse in cloudposse/atmos

Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets

Apache-2.0Auto-check passedDevOps & Cloud

Install Atmos Modernization

skills CLI
$ npx skills add cloudposse/atmos --skill atmos-modernization -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cloudposse/atmos atmos-modernization --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agent-skills/skills/atmos-modernization .claude/skills/atmos-modernization && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
atmos-modernization
GitHub stars
1.4k
Token cost
~1.8k tokens
SKILL.md length
653 words
Files
1
Skills in repo
70
Repo updated
First seen
Licence
Apache-2.0

At a glance

Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets

  • Works in 5 steps: Inspect current project behavior with… → Replace one class of legacy pattern at a… → Preserve resolved stack output unless… → …
  • Tasks that involve Legacy modernization
  • SKILL.md covers Modernization Checklist, Process, YAML Function Quoting and Native CI Direction, plus 4 more sections
  • Calls apt-get

What it does

Atmos Modernization is an agent skill from cloudposse/atmos. Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Legacy modernization and GitOps. It works with Terraform and GitHub Actions. The repository describes itself as: Atmos is the open-source runtime for infrastructure — it builds, authenticates, and ships Terraform, OpenTofu, Packer, Ansible, Kubernetes, Helm, and containers the same way on… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Legacy modernization
  • Tasks that involve GitOps

Example prompts

  • “Use the atmos-modernization skill to atmo Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift…”
  • “/atmos-modernization”

Requirements

  • Docker

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Inspect current project behavior with atmos describe stacks, atmos list components, and
  2. Replace one class of legacy pattern at a time.
  3. Preserve resolved stack output unless the modernization intentionally changes behavior.
  4. Validate with atmos describe component -s before changing CI.
  5. Update CI last, after stack config and auth patterns are current.

What it can do on your machine

Read from SKILL.md and the folder at commit 36726ae. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • apt-get

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Atmos Modernization loads about 1.8k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 653 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~50
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cloudposse/atmos at commit 36726ae, republished under its Apache-2.0 licence (© cloudposse). 653 words, ~1,828 tokens.

Download SKILL.mdSave it as .claude/skills/atmos-modernization/SKILL.md (or your agent's skills folder).
name
atmos-modernization
description
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, name_template, and declared secrets
metadata.copyright
Copyright Cloud Posse, LLC 2026
metadata.version
1.0.0
metadata.category
state-versioning

Atmos Modernization

Use this skill when updating older Atmos projects to current conventions. "Atmos Modernization" is the umbrella term for replacing legacy patterns with supported, current patterns.

Modernization Checklist

Legacy patternReplace with
name_patternname_template or explicit stack name
settings.depends_ondependencies.components
Custom command type: component/type: stack on arguments, or semantic_type: component/semantic_type: stack on flagsprovides: component/provides: stack on both arguments and flags
cloudposse/github-action-atmos* wrapper actionsNative CI with direct atmos commands
cloudposse/github-action-atmos-component-updateratmos vendor update --pull-request with native GitHub PR publishing
cloudposse/github-action-setup-atmos as defaultGitHub Actions container ghcr.io/cloudposse/atmos:<version>
apt-get install docker.io in an Atmos container jobRemove it: the official Atmos image already ships with docker.io
GitHub Actions concurrency around jobs or workflows that invoke atmosAn explicit promotion workflow or deployment controller — environments and merge queues are approval/merge-order controls, not deployment-order guarantees; a concurrency group evicts its pending run regardless of cancel-in-progress
hashicorp/setup-terraform / opentofu/setup-opentofu in Atmos jobsAtmos dependencies.tools and toolchain
Manual atmos toolchain install <tool> preinstall steps for Atmos-owned toolsDeclarative dependencies.tools at the owning component, workflow, hook, or custom command
Large inline workflow/custom-command shell scripts, repeated echo, shell loops, ad hoc sleepsNative step types such as atmos, toast, table, parallel, matrix, wait, container, emulator, and http
Hand-rolled scheduled drift GitHub ActionsAtmos Pro drift detection
cloudposse/github-action-atmos-terraform-drift-*settings.pro.drift_detection plus atmos terraform plan --upload-status
Secret values through raw store callsDeclared secrets.vars plus !secret
Legacy hook event spellingModern dotted lifecycle events such as after.terraform.plan
Static GitHub tokens in URLsAtmos Auth github/sts through Atmos Pro
cloudposse/terraform-aws-components sourcesRepos in the cloudposse-terraform-components organization
Parser-specific doubled double quotes ("") in !terraform.state or !terraform.output expressionsDirect YQ expressions; quote only as required by YAML

Process

  1. Inspect current project behavior with atmos describe stacks, atmos list components, and atmos validate stacks.
  2. Replace one class of legacy pattern at a time.
  3. Preserve resolved stack output unless the modernization intentionally changes behavior.
  4. Validate with atmos describe component <component> -s <stack> before changing CI.
  5. Update CI last, after stack config and auth patterns are current.

YAML Function Quoting

Older stack manifests may wrap an entire YQ expression in double quotes and double its inner double quotes. That parser-specific escaping is obsolete: !terraform.state and !terraform.output parse the component, optional stack, and remaining expression directly.

Replace legacy string-default quoting:

yaml
# Before
username: !terraform.output config ".username // ""default-user"""

# After
username: !terraform.output config .username // "default-user"

Replace legacy string-concatenation quoting:

yaml
# Before
postgres_url: !terraform.state aurora-postgres ".master_hostname | ""jdbc:postgresql://"" + . + "":5432/events"""

# After
postgres_url: !terraform.state 'aurora-postgres .master_hostname | "jdbc:postgresql://" + . + ":5432/events"'

The outer single quotes in the concatenation example are YAML quoting, not function-parser escaping. Use YAML quoting only when the scalar requires it; for complete YAML and YQ quoting guidance, see the atmos-yaml-functions skill.

Show full SKILL.md (238 more words)Show less

Native CI Direction

New CI should run Atmos directly, preferably in the Atmos container image:

yaml
jobs:
  plan:
    runs-on: ubuntu-latest
    container:
      image: ghcr.io/cloudposse/atmos:${{ vars.ATMOS_VERSION }}
    permissions:
      contents: read
      id-token: write
    steps:
      - uses: actions/checkout@v6
      - run: atmos terraform plan vpc -s prod

The official Atmos image includes docker.io, so do not add an apt-get install docker.io step to containerized Atmos jobs. Docker-backed commands use the runner-provided Docker daemon/socket.

Use atmos describe affected --format=matrix for PR matrices and atmos list instances --format=matrix for full estate operations.

Component Updater Migration

Replace the legacy Component Updater action with checkout plus atmos vendor update --pull-request. Keep update selection under vendor.update (including named groups) and PR/summary policy under vendor.ci. Grant only contents: write, pull-requests: write, and issues: write where needed. Atmos writes a native GitHub step summary for every vendor update; it links to any created or reused PR. Do not use third-party actions for update, commit, push, or PR creation. For exact configuration and staged migration, use the vendoring component-updater reference and migration from-component-updater reference.

Drift Direction

Atmos Pro is the product path for drift detection. Enable drift per stack/component:

yaml
settings:
  pro:
    enabled: true
    drift_detection:
      enabled: true

Then upload plan status:

bash
atmos terraform plan vpc -s prod --upload-status

Dependencies Direction

Use dependencies.components for component, file, and folder dependencies:

yaml
dependencies:
  components:
    - component: vpc
    - component: dns-zone
      stack: plat-ue2-prod
    - kind: file
      path: configs/service.yaml
    - kind: folder
      path: src/lambda

Treat settings.depends_on as migration-only syntax.

Component Source Repository Direction

Check source, vendor.yaml, component.yaml, Terraform module sources, and documentation examples for cloudposse/terraform-aws-components. That monorepo is deprecated; components moved to individual repositories in the cloudposse-terraform-components organization.

For example, migrate VPC references from the old monorepo form:

yaml
source: "github.com/cloudposse/terraform-aws-components.git//modules/vpc?ref=1.450.0"

to the component repository form:

yaml
source: "github.com/cloudposse-terraform-components/aws-vpc.git?ref=1.450.0"

Keep versions pinned when changing sources, and validate the target repository/tag exists before updating production stacks.

© cloudposse, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in agent-skills/skills/atmos-modernization of cloudposse/atmos.

Open the folder on GitHubat commit 36726ae

Compare with similar skills

Atmos Modernization next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Atmos Modernization compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Atmos Modernization this skillcloudposse/atmos1.4k—~1.8kAutomated safety check: PassApache-2.0
Devops Excellencemajiayu000/spellbook286—~2.4kAutomated safety check: NotesMIT
Devops EngineerYikai-Liao/symusic1891 repos~1.5kAutomated safety check: PassMIT
Devops Automatorcuriositech/some_claude_skills243—~1.8kAutomated safety check: PassMIT
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2606 repos~1.1kAutomated safety check: NotesCustom licence
CI CDEliasOulkadi/shokunin114—~3.4kAutomated safety check: NotesMIT

Similar skills

  • Devops Excellence

    majiayu000/spellbook

    DevOps and CI/CD expert. An agent skill from majiayu000/spellbook.

    286 GitHub stars~2.4k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Devops Engineer

    Yikai-Liao/symusic

    Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates.

    189 GitHub starsUsed in 1 repo~1.5k tokens
    DevOps & CloudAuto-check passed
  • Devops Automator

    curiositech/some_claude_skills

    Expert DevOps engineer for CI/CD, IaC, Kubernetes, and deployment automation.

    243 GitHub stars~1.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    260 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes
  • CI CD

    EliasOulkadi/shokunin

    Design CI/CD pipelines for GitHub Actions, GitLab CI, and CircleCI with matrix builds, test sharding, caching, Docker layer caching, OIDC auth, deployment strategies (rolling, blue-green, canary)…

    114 GitHub stars~3.4k tokensUpdated 3 days ago
    DevOps & CloudAuto-check: notes
  • Gitops Knowledge

    fluxcd/agent-skills

    Flux CD and Flux Operator expert — answers questions and generates schema-validated YAML for all Flux CRDs (not repo auditing or live cluster debugging).

    231 GitHub stars~3.8k tokensUpdated 6 days ago
    DevOps & CloudAuto-check passed

More from cloudposse/atmos

All 70 skills in this repo
  • Fix Log

    cloudposse/atmos

    A skill your agent uses when implementing, finishing, documenting, or reviewing a fix, repair, remediation, bug fix, debug-and-fix task, workflow fix, infrastructure fix, or any change that should…

    1.4k GitHub stars~685 tokensUpdated today
    Auto-check passed
  • Atmos Lint

    cloudposse/atmos

    Atmos Terraform linting with TFLint: standalone atmos terraform lint, component-aware config discovery and toolchain versions, TFLint rule configuration, and lifecycle hooks/CI findings.

    1.4k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Changelog

    cloudposse/atmos

    Blog post authoring for Atmos: MDX template, frontmatter, website/blog/tags.yml and authors.yml rules, problem-first framing, backtick-opening ban, optional cast embeds, and no-Go-internals leakage.

    1.4k GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • Editions

    cloudposse/atmos

    Decide whether a PR's new or changed default needs edition-journal handling (pkg/edition, docs/prd/editions.md), and do the mechanical work if so: journal entries, the four-layer default check…

    1.4k GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Atmos Migration

    cloudposse/atmos

    Migrate to Atmos from native Terraform, Terraform Workspaces, Terramate, Terragrunt, Make, Just, or Task; migrate tool versions from mise or Aqua CLI; migrate AWS/GCP/Azure CLI configs, Leapp…

    1.4k GitHub stars~5.1k tokensUpdated today
    Auto-check: warnings
  • PR Maintenance Loop

    cloudposse/atmos

    Start an hourly background loop that keeps the current branch's PR rebased, its addressed CodeRabbit threads resolved, its CI checks passing, its lint clean, its tests passing with adequate patch…

    1.4k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Questions about Atmos Modernization

What does Atmos Modernization do?

Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets. Atmos Modernization is an agent skill from cloudposse/atmos.

When should I use Atmos Modernization?

Atmos Modernization fits situations like: tasks that involve Legacy modernization; tasks that involve GitOps.

How do I install Atmos Modernization in Claude Code?

Run `npx skills add cloudposse/atmos --skill atmos-modernization -a claude-code`. Or copy the skill folder (agent-skills/skills/atmos-modernization in cloudposse/atmos) into .claude/skills/atmos-modernization in your project. Claude Code loads it when a task matches its description.

How do I install Atmos Modernization in Codex?

Run `npx skills add cloudposse/atmos --skill atmos-modernization -a codex`. Or copy the skill folder (agent-skills/skills/atmos-modernization in cloudposse/atmos) into .agents/skills/atmos-modernization in your project. Codex loads it when a task matches its description.

Can I use Atmos Modernization in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cloudposse/atmos --skill atmos-modernization -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/atmos-modernization, .gemini/skills/atmos-modernization, .github/skills/atmos-modernization and .opencode/skills/atmos-modernization in your project.

What does Atmos Modernization need to run?

Going by SKILL.md and its folder, Atmos Modernization needs the command-line tools its instructions call (apt-get). Our summary lists: Docker.

Does Atmos Modernization access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Atmos Modernization safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Atmos Modernization use?

Atmos Modernization is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Atmos Modernization use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Atmos Modernization?

Skills that share tags, products or a category with Atmos Modernization: Devops Excellence (majiayu000/spellbook, 286 stars), Devops Engineer (Yikai-Liao/symusic, 189 stars), Devops Automator (curiositech/some_claude_skills, 243 stars) and Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Atmos Modernization?

cloudposse (a GitHub organization) maintains it in cloudposse/atmos, which has 1,396 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 8, 2026.

Source: cloudposse/atmos on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.