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/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/component-development)<a href="https://agentmods.dev/skills/cloudposse/atmos/component-development"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/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/component-development"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/component-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 82 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.00044 | $0.01550 |
| Opus 5.5 | $0.00018 | $0.00620 |
| Sonnet 5.5 | $0.00009 | $0.00310 |
| Haiku 4.5 | $0.00004 | $0.00155 |
Grade A, and why
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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Development
Use this skill when adding or changing an Atmos native component type or shared component behavior.
Start With The Existing Contract
Inspect comparable component types before designing:
rg -n "ComponentType|SectionName|components\\..*base_path" pkg/config pkg/schema
rg -n "component.Register|ComponentProvider|Execute\\(" pkg/component cmd internal
rg -n "process.*ComponentsIndexed|ExecuteGraph|dependencies.components" internal pkg
For stack-surface decisions, compare Terraform, Helmfile, Packer, and Ansible. Reuse shared sections when they already exist:
metadatavarsenvsettingshooksauthdependenciesgeneratesourceprovision
Do not invent nested settings for component-owned inputs. If an instance is components.<type>.<name>, component-specific inputs belong directly under that instance, e.g. components.kubernetes.argocd.paths, not settings.kubernetes.paths.
Required Wiring
For a new component type, update all applicable surfaces in one PR:
- Constants:
pkg/config/const.go - CLI/default config structs:
pkg/schema/schema.go - Defaults:
pkg/config/default.go - Config path resolution:
pkg/config/config.go,pkg/utils/component_path_utils.go - Component registry provider:
pkg/component/<type>/ - Command package:
cmd/<type>/ - Root side-effect imports:
cmd/root.go - Source provisioning base path support:
pkg/provisioner/source/ - Hooks/events if lifecycle hooks are supported:
pkg/hooks/ - Affected detection:
internal/exec/describe_affected_* - DAG/bulk execution if
--allor--affectedis supported - Embedded CLI usage examples:
cmd/markdown/atmos_<command>*_usage.md - Runtime stack schemas:
pkg/datafetcher/schema/atmos/manifest/1.0.jsonandpkg/datafetcher/schema/stacks/stack-config/1.0.json - LSP hints if stack authoring changes:
pkg/lsp/server/ - Docs: command docs, stack component docs,
atmos.yamlconfig docs - Examples under
examples/for user-visible component types
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 · 161 lines · 44 tokens per session scan A 52eade3a397f
component-development is a skill published in the GitHub repository cloudposse/atmos (1,403 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 1,550 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-08-30.
Other skills, from other repositories
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.
gke-basics
Trigger: Use when working with Google Kubernetes Engine basics — cluster setup, node pools, workloads, networking, and storage fundamentals.
aiox-qa
Activate Quinn (qa) for Test Architect & Quality Advisor. Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requirements traceability, risk assessment, and...
architect-first
Guide for implementing the Architect-First development philosophy - perfect architecture, pragmatic execution, quality guaranteed by tests. Use this skill when starting new features, refactoring systems, or when architectural decisions are needed. Enforces non-negotiables like complete design/documentation before…
review-story
QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, qa-gate, /review-story.