Skip to content
Back to search

cloudposse

Official Atmos plugins and skills for Claude Code

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 12 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/cloudposse/atmos with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/cloudposse/atmos'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/cloudposse--atmos/badge.svg)](/listings/cloudposse--atmos)

HTML

<a href="/listings/cloudposse--atmos"><img src="/api/listings/cloudposse--atmos/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 18 lines
  1. {
  2. "name": "cloudposse",
  3. "version": "1.234.1",
  4. "description": "Official Atmos plugins and skills for Claude Code",
  5. "owner": {
  6. "name": "Cloud Posse",
  7. "email": "opensource@cloudposse.com"
  8. },
  9. "plugins": [
  10. {
  11. "name": "atmos",
  12. "version": "1.234.1",
  13. "source": "./agent-skills",
  14. "description": "Atmos skills for AI coding assistants: Terraform/Helmfile/Packer/Ansible orchestration, stacks, remote imports, containers, emulators, Native CI, Atmos Pro, Auth, GitOps, secrets, cache, hooks, workflows, YAML functions, and modernization.",
  15. "category": "development"
  16. }
  17. ]
  18. }
README.md · README · 226 lines
  1. <!-- markdownlint-disable -->
  2. <a href="https://cpco.io/homepage"><img src="https://github.com/cloudposse/atmos/blob/main/.github/banner.png?raw=true" alt="Project Banner"/></a><br/>
  3. <p align="right">
  4. <a href="https://github.com/cloudposse/atmos/releases/latest"><img src="https://img.shields.io/github/release/cloudposse/atmos.svg?style=for-the-badge" alt="Latest Release"/></a><a href="https://github.com/cloudposse/atmos/commits/main/"><img src="https://img.shields.io/github/last-commit/cloudposse/atmos/main?style=for-the-badge" alt="Last Updated"/></a><a href="https://github.com/cloudposse/atmos/actions/workflows/test.yml"><img src="https://img.shields.io/github/actions/workflow/status/cloudposse/atmos/test.yml?style=for-the-badge" alt="Tests"/></a><a href="https://scorecard.dev/viewer/?uri=github.com/cloudposse/atmos"><img src="https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fapi.scorecard.dev%2Fprojects%2Fgithub.com%2Fcloudposse%2Fatmos&query=%24.score&label=openssf%20scorecard&style=for-the-badge" alt="OpenSSF Scorecard"/></a><a href="https://slack.cloudposse.com"><img src="https://slack.cloudposse.com/for-the-badge.svg" alt="Slack Community"/></a></p>
  5. <!-- markdownlint-restore -->
  6. <!--
  7. ** DO NOT EDIT THIS FILE
  8. **
  9. ** This file was automatically generated by the `cloudposse/build-harness`.
  10. ** 1) Make all changes to `README.yaml`
  11. ** 2) Run `make init` (you only need to do this once)
  12. ** 3) Run`make readme` to rebuild this file.
  13. **
  14. ** (We maintain HUNDREDS of open source projects. This is how we maintain our sanity.)
  15. **
  16. -->
  17. **Run your infrastructure anywhere.**
  18. Atmos is the open-source **runtime for infrastructure** — it builds, authenticates, and ships Terraform, OpenTofu, Kubernetes, Helm, and containers the same way on your laptop, in CI, and with AI agents. Auth, secrets, vendoring, caching, the toolchain, workflows, and CI are built in. Point every environment at the same reusable root modules and treat the rest as configuration. Stop stringing together 25 tools.
  19. > **Run it on your laptop. Run it the same in CI. Run it with agents.**
  20. Everything is open source and free.
  21. > [!TIP]
  22. > ### You can try out `atmos` directly in your browser using GitHub Codespaces
  23. >
  24. > [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://github.com/codespaces/new?hide_repo_select=true&ref=main&repo=cloudposse/atmos&skip_quickstart=true)
  25. >
  26. > <i>Already start one? Find it [here](https://github.com/codespaces).</i>
  27. >
  28. ## Screenshots
  29. <img src="docs/demo.gif" alt="Demo" />*<br/>Example of running atmos to describe infrastructure.*
  30. ## Introduction
  31. [Atmos](https://atmos.tools) turns sprawling cloud infrastructure into one declarative system you can run consistently — locally, in CI/CD, and through AI agents. Model your platform once as [stacks](https://atmos.tools/stacks) and [components](https://atmos.tools/components), authenticate once, and run the same commands everywhere. The same code deploys to every region, environment, and stage with [DRY configuration](https://atmos.tools/design-patterns/) — no copy-paste, no bespoke wrapper scripts, no glue.
  32. [Cloud Posse](https://cloudposse.com/) builds and operates production infrastructure on AWS, Azure, and GCP with Atmos every day — and so do startups and enterprises managing thousands of components.
  33. ## Everything you'd otherwise bolt on
  34. Auth, secrets, vendoring, caching, the toolchain, workflows, CI, and AI are part of the runtime — not a pile of plugins you wire together.
  35. - [**Unified Auth:**](https://atmos.tools/cli/configuration/auth) One identity layer across AWS, Azure, and GCP — SSO, OIDC, and federation. EKS and ECR login happen automatically, and the same identity feeds Terraform, stores, and emulators.
  36. - [**Secrets Management:**](https://atmos.tools/cli/configuration/secrets) Declare secrets per environment, source them from 10+ backends (1Password, SSM, Vault, SOPS, and more), and mask them across every channel.
  37. - [**Vendoring:**](https://atmos.tools/cli/configuration/vendor) Pull every dependency just-in-time with version pinning and retries — no separate vendor step.
  38. - [**Caching & Mirroring:**](https://atmos.tools/cli/configuration/ci/cache) A native build cache plus a transparent Terraform provider and module registry mirror — warm in CI, instant on your laptop.
  39. - [**Toolchain:**](https://atmos.tools/cli/configuration/toolchain) Auto-install the exact Terraform, OpenTofu, and Helmfile versions your stacks need — verified by checksum.
  40. - [**Workflows & Automation:**](https://atmos.tools/workflows) Orchestrate, automate, and chain anything with 25+ step types and custom commands across every component.
  41. - [**GitOps & CI/CD:**](https://atmos.tools/ci) The same commands locally and in CI. Detect affected components, emit matrices, and catch drift.
  42. - [**AI + MCP:**](https://atmos.tools/ai) Chat about your infrastructure, run 20+ skills, expose Atmos as an MCP server, or add `--ai` to any command.
  43. ## Run anything, the same way
  44. - **Terraform & OpenTofu like a platform team.** Plan and apply across every component in dependency order with bounded concurrency. Backends and providers are generated for you, and drift is caught automatically.
  45. - **Kubernetes & Helm as first-class workloads.** Model [Helmfile](https://atmos.tools/components/helmfile) and Kubernetes releases beside the rest of your stack, with the same CLI you already use for Terraform.
  46. - **Containers and cloud emulators.** [Containers](https://atmos.tools/components/container) and dev containers are workloads too — and you can spin up [cloud emulators](https://atmos.tools/components/emulator) locally so your whole stack runs on your laptop, with no account required to iterate.
  47. - **Bring your own.** [Packer](https://atmos.tools/components/packer), [Ansible](https://atmos.tools/components/ansible), or your own [component types](https://atmos.tools/components) plug into the same registry the built-ins use.
  48. ## Your laptop is the CI. CI is your laptop.
  49. Same command, same auth, same secrets, same toolchain — whether you run it locally or in a pipeline. Atmos is git-aware: it detects what changed and plans or applies only the affected components, so CI does exactly the work that changed — nothing more.
  50. ## Built for your agents
  51. Everything is declarative and self-documenting, so AI agents can reason about your infrastructure instead of stringing together 25 tools and praying. Atmos ships a catalog of portable [agent skills](https://atmos.tools/ai/agent-skills) — working across Claude Code, Cursor, Gemini, and Copilot — and an [MCP server](https://atmos.tools/ai/mcp-server) so any agent can install what it needs and drive Atmos directly, as native tools, with no custom integration.
  52. ## Extend it without forking it
  53. - [**Custom Commands:**](https://atmos.tools/cli/configuration/commands) Wrap any script as a first-class `atmos` command with flags, args, and identity.
  54. - [**YAML Functions:**](https://atmos.tools/functions/yaml) Resolve state, outputs, secrets, and Git metadata right inside your config.
  55. - [**Hooks:**](https://atmos.tools/stacks/hooks) Run infracost, checkov, trivy, or any command on lifecycle events.
  56. - [**Stores:**](https://atmos.tools/cli/configuration/stores) Plug in SSM, Secrets Manager, Key Vault, Vault, Redis, and more for cross-component data.
  57. - [**Validation:**](https://atmos.tools/validation/validating) Enforce your own guardrails with OPA/Rego policies and JSON Schema.
  58. - [**Templates & Data Sources:**](https://atmos.tools/templates) Pull live data into your config with Go templates and Gomplate datasources.
  59. ## Use Cases
  60. Atmos has consistently proven its strength across the cloud infrastructure and DevOps domains:
  61. - **Managing Large Multi-Account Cloud Environments:** Suitable for organizations using multiple cloud accounts to separate different
  62. projects or stages of development.
  63. - **Cross-Platform Cloud Architectures:** Ideal for businesses that need to manage configuration of services across AWS, GCP, Azure, etc., to
  64. build a cohesive system.
  65. - **Multi-Tenant Systems for SaaS:** Perfect for SaaS companies looking to host multiple customers within a unified infrastructure.
  66. Define a baseline tenant configuration once, then onboard new tenants by reusing this baseline through pure configuration — no further code required.
  67. - **Efficient Multi-Region Deployments:** Define baseline configurations with [stacks](https://atmos.tools/stacks) and extend them across regions
  68. with DRY principles through [imports](https://atmos.tools/stacks/imports) and [inheritance](https://atmos.tools/howto/inheritance).
  69. - **Compliant Infrastructure for Regulated Industries:** Create vetted configurations that comply with SOC2, HIPAA, HITRUST, PCI, and other
  70. standards, then share and reuse them across the organization via [service catalogs](https://atmos.tools/howto/catalogs),
  71. [component libraries](https://atmos.tools/components), [vendoring](https://atmos.tools/vendor), and [OPA policies](https://atmos.tools/validation/opa).
  72. - **Empowering Teams with Self-Service Infrastructure:** Let teams manage their infrastructure independently, using predefined templates and policies.
  73. > [!TIP]
  74. > Don't see your use-case listed? Ask us in the [`#atmos`](https://slack.cloudposse.com) Slack channel,
  75. > or [join us for "Office Hours"](https://cloudposse.com/office-hours/) every week.
  76. ## Telemetry
  77. Atmos collects **anonymous telemetry** to help improve the product by understanding how it's used.
  78. You can **opt-out** of telemetry collection in either of the following ways:
  79. - Set `settings.telemetry.enabled: false` in your `atmos.yaml`
  80. - Or set the environment variable: `ATMOS_TELEMETRY_ENABLED=false`
  81. > **Note for Atmos Pro users:** If you're using [Atmos Pro](https://atmos-pro.com), your [workspace ID](https://atmos-pro.com/docs/authentication/workspace-id) will be included in telemetry events. This allows our team to provide more effective support and assist with troubleshooting as part of your subscription.
  82. To learn more about what is collected and how it works, see the [Telemetry Documentation](https://atmos.tools/cli/telemetry).
  83. ## Documentation
  84. Find all documentation at: [atmos.tools](https://atmos.tools)
  85. ## ✨ Contributing
  86. This project is under active development, and we encourage contributions from our community.
  87. Many thanks to our outstanding contributors:
  88. <a href="https://github.com/cloudposse/atmos/graphs/contributors">
  89. <img src="https://contrib.rocks/image?repo=cloudposse/atmos&max=24" />
  90. </a>
  91. For 🐛 bug reports & feature requests, please use the [issue tracker](https://github.com/cloudposse/atmos/issues).
  92. In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
  93. 1. Review our [Code of Conduct](https://github.com/cloudposse/atmos/?tab=coc-ov-file#code-of-conduct) and [Contributor Guidelines](https://github.com/cloudposse/.github/blob/main/CONTRIBUTING.md).
  94. 2. **Fork** the repo on GitHub
  95. 3. **Clone** the project to your own machine
  96. 4. **Commit** changes to your own branch
  97. 5. **Push** your work back up to your fork
  98. 6. Submit a **Pull Request** so that we can review your changes
  99. **NOTE:** Be sure to merge the latest changes from "upstream" before making a pull request!
  100. ### 🌎 Slack Community
  101. Join our [Open Source Community](https://cpco.io/slack?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/atmos&utm_content=slack) on Slack. It's **FREE** for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally *sweet* infrastructure.
  102. ### 📰 Newsletter
  103. Sign up for [our newsletter](https://cpco.io/newsletter?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/atmos&utm_content=newsletter) and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know.
  104. Dropped straight into your Inbox every week — and usually a 5-minute read.
  105. ### 📆 Office Hours <a href="https://cloudposse.com/office-hours?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/atmos&utm_content=office_hours"><img src="https://img.cloudposse.com/fit-in/200x200/https://cloudposse.com/wp-content/uploads/2019/08/Powered-by-Zoom.png" align="right" /></a>
  106. [Join us every Wednesday via Zoom](https://cloudposse.com/office-hours?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/atmos&utm_content=office_hours) for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a _live Q&A_ that you can’t find anywhere else.
  107. It's **FREE** for everyone!
  108. ## License
  109. <a href="https://opensource.org/licenses/Apache-2.0"><img src="https://img.shields.io/badge/License-Apache%202.0-blue.svg?style=for-the-badge" alt="License"></a>
  110. <details>
  111. <summary>Preamble to the Apache License, Version 2.0</summary>
  112. <br/>
  113. <br/>
  114. Complete license is available in the [`LICENSE`](LICENSE) file.
  115. ```text
  116. Licensed to the Apache Software Foundation (ASF) under one
  117. or more contributor license agreements. See the NOTICE file
  118. distributed with this work for additional information
  119. regarding copyright ownership. The ASF licenses this file
  120. to you under the Apache License, Version 2.0 (the
  121. "License"); you may not use this file except in compliance
  122. with the License. You may obtain a copy of the License at
  123. https://www.apache.org/licenses/LICENSE-2.0
  124. Unless required by applicable law or agreed to in writing,
  125. software distributed under the License is distributed on an
  126. "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  127. KIND, either express or implied. See the License for the
  128. specific language governing permissions and limitations
  129. under the License.
  130. ```
  131. </details>
  132. ## Trademarks
  133. All other trademarks referenced herein are the property of their respective owners.
  134. ---
  135. Copyright © 2017-2026 [Cloud Posse, LLC](https://cpco.io/copyright)
  136. <a href="https://cloudposse.com/readme/footer/link?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/atmos&utm_content=readme_footer_link"><img alt="README footer" src="https://cloudposse.com/readme/footer/img"/></a>
  137. <img alt="Beacon" width="0" src="https://ga-beacon.cloudposse.com/UA-76589703-4/cloudposse/atmos?pixel&cs=github&cm=readme&an=atmos"/>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.