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-gitgit 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-git)<a href="https://agentmods.dev/skills/cloudposse/atmos/atmos-git"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/atmos-git.svg" alt="Measured on agentmods" height="20"></a>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.00054 | $0.01024 |
| Opus 5 | $0.00027 | $0.00512 |
| Sonnet 5 | $0.00011 | $0.00205 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
atmos-git 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 3d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atmos Git
Use this skill for native Git repository management, GitOps automation, managed workdirs, local Git hook shims, signed commits, and GitHub auth through Atmos Auth or Atmos Pro STS.
Related Skills
| Need | Load |
|---|---|
| Atmos Pro GitHub App commits | atmos-pro |
github/sts credentials for private repos |
atmos-auth |
Lifecycle git hooks |
atmos-hooks |
| Modernizing old GitHub Actions GitOps patterns | atmos-modernization |
Configuration
Configure managed repositories in atmos.yaml:
git:
repositories:
deployment:
uri: https://github.com/acme/deployment.git
branch: main
auth:
identity: atmos-pro
commit:
author:
name: Atmos Bot
email: [email protected]
signing: auto # auto | always | never
Use identities or github/sts for private GitHub access. Do not put tokens in repository URIs.
Commands
| Command | Purpose |
|---|---|
atmos git list |
List configured repositories |
atmos git clone <name-or-uri> |
Clone or reconcile a managed repository |
atmos git init <name-or-path> |
Initialize a managed repository |
atmos git pull <name-or-path> |
Fast-forward pull |
atmos git status <name-or-path> |
Show working tree status |
atmos git diff <name-or-path> |
Show changes |
atmos git commit <name-or-path> --message "msg" |
Stage managed paths and commit |
atmos git push <name-or-path> |
Push commits |
atmos git clean <name> |
Remove managed workdirs |
Use atmos git hooks install, run, and uninstall for local Git hook shims in the current
repository.
GitOps Guidance
- Use managed repositories for deployment repos, generated config repos, and promotion workflows.
- Use signed commits where repository policy requires them; prefer
commit.signing: autounless the workflow requiresalwaysornever. - Use
github/stsin CI so Git subprocesses receive short-lived GitHub App credentials. - Use
atmos pro commitwhen CI-generated commits must trigger follow-on GitHub Actions workflows. - Keep generated commits traceable with clear messages and commit trailers when the project uses provenance conventions.
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.
- 3d ago First seen · 90 lines · 54 tokens per session scan A c298f9c71b96
atmos-git is a skill published in the GitHub repository cloudposse/atmos (1,372 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 1,024 once invoked, about $0.0003 per session on Opus 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
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
contributing
Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.
commit-msg
You receive a git diff of staged changes via stdin. Generate a commit message.
lore-commit
A Git commit-writing guide that records the reasoning behind a change alongside its commit message. It defines commit types and structured notes for constraints, rejected options, confidence, risk, testing, and follow-up work.
cap-commit-push
Use when the user sends cap or asks for a fast commit-and-push shortcut for current repository changes.