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/atmos-core-component-development/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/atmos-core-component-development)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-core-component-development"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-core-component-development/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-core-component-development"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-core-component-development.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.00080 | $0.01403 |
| Opus 5.5 | $0.00032 | $0.00561 |
| Sonnet 5.5 | $0.00016 | $0.00281 |
| Haiku 4.5 | $0.00008 | $0.00140 |
Grade A, and why
atmos-core-component-development 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Core: Component Type Development
Use this skill when developing Atmos itself — adding or modifying a component type (kind) in the
Go codebase. This is contributor/core guidance, distinct from the user-facing atmos-components skill
(which documents authoring terraform/helmfile/container components in stacks).
Start from docs/developing-component-plugins.md (the component-plugin development guide). The notes
below capture the non-obvious wiring learned while adding the container component type.
The component provider (pkg/component)
A component type is a ComponentProvider (pkg/component/provider.go) registered via init() with
component.Register(...) (pkg/component/registry.go). Reference impls:
pkg/component/ansible/— typed-config built-in style.pkg/component/mock/,pkg/component/custom/— thePlugins-map plugin style.pkg/component/container/— provider +cmd/lifecycle split.
Layout per the guide: config.go (typed Config + parseConfig), <type>.go (provider + init),
executor.go (verb implementations), <type>_test.go (>90% coverage). Wire a blank import into
cmd/root.go so init() runs.
Reusable error sentinels live in errors/errors.go: ErrComponentExecutionFailed,
ErrComponentConfigInvalid, ErrComponentValidationFailed, ErrComponentTypeEmpty.
First-class component config (NOT vars)
Per-instance config that is not arbitrary template data must be first-class top-level sections
(siblings of metadata/env/composition), NOT nested under vars. For container, the config reuses
the workflow container-step structs (schema.ContainerBuildStep/ContainerRunStep/ContainerMount/
ContainerPort in pkg/schema/workflow.go) for consistency. Decode a YAML-derived map[string]any
into those structs with mapstructure using TagName: "yaml" so snake_case keys (build_args,
read_only) map.
The CLI command group (cmd/)
Mirror cmd/ansible/: a base cobra.Command registered through the command registry
(cmd/internal CommandProvider), persistent flags via flags.NewStandardParser() (NEVER
viper.BindEnv/BindPFlag), one thin file per verb dispatching to
component.MustGetProvider(<type>).Execute(&component.ExecutionContext{...}). Wire a blank import into
cmd/root.go.
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 · 96 lines · 80 tokens per session scan A 5ce757a76fcf
atmos-core-component-development is a skill published in the GitHub repository cloudposse/atmos (1,405 stars, last pushed today), licensed Apache-2.0. It adds 80 tokens to every session and 1,403 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
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
lovable
Lovable MCP tool usage — deploy projects, message agent, test with agent-browser. Minimize credits by delegating to local repo.
agent-browser
Browser automation via Chrome/Chromium CDP — open, snapshot, click, screenshot. For testing web apps, mobile layouts, and automated interactions without Playwright/Puppeteer.
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".