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-secretsgit 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-secrets)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-secrets"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-secrets/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-secrets"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-secrets.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.00047 | $0.00787 |
| Opus 5.5 | $0.00019 | $0.00315 |
| Sonnet 5.5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
atmos-secrets 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Secrets
Use this skill for declared secrets, secret backends, and the atmos secret command family.
Secrets must be declared before they can be set, read, injected, or resolved with !secret.
Related Skills
| Need | Load |
|---|---|
| Store-backed non-secret values | atmos-stores |
YAML !secret and !store functions |
atmos-yaml-functions |
| Auth identity for secret backend access | atmos-auth |
| Local Vault/OpenBao testing | atmos-emulator |
Declare Secrets
Declare secrets under component secrets.vars and keep Terraform inputs secret-aware:
components:
terraform:
app:
secrets:
vars:
DATADOG_API_KEY:
description: Datadog API key
store: prod/ssm
required: true
vars:
datadog_api_key: !secret DATADOG_API_KEY
Supported backend families include AWS SSM, AWS Secrets Manager, HashiCorp Vault, Azure Key Vault, GCP Secret Manager, 1Password, and SOPS-encrypted files.
Commands
| Command | Purpose |
|---|---|
atmos secret list -s <stack> -c <component> |
List declared secrets and status |
atmos secret init -s <stack> -c <component> |
Provision/rotate declared secrets interactively |
atmos secret set <name> -s <stack> -c <component> |
Set a declared secret |
atmos secret get <name> -s <stack> -c <component> |
Retrieve a declared secret, masked by default |
atmos secret import -s <stack> -c <component> |
Bring existing backend secrets under management |
atmos secret pull -s <stack> -c <component> |
Download declared secrets to a local file |
atmos secret push -s <stack> -c <component> |
Upload declared secrets from a local file |
atmos secret shell -s <stack> -c <component> |
Start a shell with secrets in environment |
atmos secret exec -s <stack> -c <component> -- <cmd> |
Run one command with secrets injected |
atmos secret validate -s <stack> -c <component> |
CI gate for required initialized secrets |
atmos secret keygen ... |
Generate key material for supported vault backends |
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 · 72 lines · 47 tokens per session scan A 95be09ab15df
atmos-secrets is a skill published in the GitHub repository cloudposse/atmos (1,403 stars, last pushed today), licensed Apache-2.0. It adds 47 tokens to every session and 787 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
gke-basics
Trigger: Use when working with Google Kubernetes Engine basics — cluster setup, node pools, workloads, networking, and storage fundamentals.
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...
managing-railway
Railway platform CLI for service deployment, infrastructure management, and debugging. Use for creating services, managing deployments, configuring networking, and reviewing logs.
github-actions
GitHub Actions CI/CD workflows for automating build, test, and deployment.
security-scanning
CI security scanning: secrets, deps, SAST, triage, expiring exceptions.