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.
Borrowing it
Nothing to install: this file belongs to cloudposse/atmos. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cloudposse/atmos/main/.claude/skills/roadmap/SKILL.mdgit 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/roadmap)<a href="https://agentmods.dev/skills/cloudposse/atmos/roadmap"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/roadmap/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/roadmap"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/roadmap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 142 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 145 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 145 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00080 | $0.02640 |
| Opus 5.5 | $0.00032 | $0.01056 |
| Sonnet 5.5 | $0.00016 | $0.00528 |
| Haiku 4.5 | $0.00008 | $0.00264 |
Grade A, and why
roadmap 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Maintainer
Use this skill to keep the Atmos roadmap page at /roadmap accurate, up-to-date, and aligned with actual
development progress.
Core Responsibilities
- Update milestone statuses inside
initiatives[].milestones[]when features ship — never promote a milestone intofeatured[]. - Link milestones to changelog entries when announcements are published — but only for user-visible
changes (see "No Changelog Posts for Internal-Only Refactors" below). For the post itself, use the
changelogskill; this skill only owns theroadmap.jslink. - Add new milestones as development plans evolve.
- Update progress percentages based on milestone completion.
- Add new quarters as time progresses.
- Add new initiatives when strategic priorities expand.
- Audit roadmap accuracy against recent releases.
Featured Items: Curated, Max 6, Do Not Modify
The featured: [] array in roadmap.js is a manually curated highlight reel of the top 6 strategic
initiatives only. It is not the changelog and not a list of every shipped milestone.
Hard cap: 6 items. If a featured slot needs to be added, an existing entry must be removed first — and only the user can decide which.
Rule: Never add, remove, or reorder entries in featured unless the user explicitly asks ("add X to
featured", "promote Y to featured", "remove Z from featured"). When you ship a milestone, update its entry
inside initiatives[].milestones[]. You do not mirror it into featured.
Bar for "featured": A featured item represents a strategic, transformative capability — e.g., "Atmos AI", "Cloud Authentication", "Native CI/CD". Per-release improvements, plumbing, and incremental enhancements never qualify, even when they are shipped.
If unsure, ask the user. Do not guess.
No Changelog Posts for Internal-Only Refactors
Changelog posts in website/blog/ are user-facing release announcements. Internal refactors with no
user-visible behavior change do NOT belong in the changelog, even when they are significant engineering
achievements (complexity reduction, test coverage improvements, function decomposition, dependency removal,
etc.).
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 · 310 lines · 80 tokens per session scan A 30750b46e24a
roadmap is a skill published in the GitHub repository cloudposse/atmos (1,403 stars, last pushed today), licensed Apache-2.0. It adds 80 tokens to every session and 2,640 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
csv
CSV data processing — view, filter, convert, merge tabular data. Zero barrier — use with x-cmd, Python, or awk. Use for "csv", "data", "table", "spreadsheet", "conversion".
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
gke-basics
Trigger: Use when working with Google Kubernetes Engine basics — cluster setup, node pools, workloads, networking, and storage fundamentals.
repo
Convention + tooling for where agent-cloned repos live and how their worktrees are arranged. Default bare repo at /.x-repo/.bare/ / / .git with linked working trees under /.x-repo/ / / [/@ ]. Discovered via x repo ls. Worktree management via x repo wt. Use for "where to clone", "git clone path", "workspace layout"…
gh
You have access to gh (GitHub CLI) for repository and project management.