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/say/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/say)<a href="https://agentmods.dev/skills/cloudposse/atmos/say"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/say/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/say"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/say.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.00058 | $0.00689 |
| Opus 5.5 | $0.00023 | $0.00276 |
| Sonnet 5.5 | $0.00012 | $0.00138 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
say 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audible Task Notifications
A written summary is easy to miss when it lands in a background session hours after the user stopped watching. This skill gives that moment an audible signal too.
When to use it
Two triggers, general-purpose — not tied to any one feature:
- A task or cycle finished in a way that needs human review (e.g. a fix was applied but the result deserves a second look).
- Execution is blocked and needs human input to proceed (e.g. a merge conflict, an ambiguous finding, a failure the caller correctly declined to touch).
Any skill or agent reaching one of these states should invoke this — it is not specific to
fix-all or any other single caller.
Phrasing rule
Keep it under ~15 words. Be specific, not a summary dump — include identifying context (a PR number, branch, or file) so the listener knows what without reading anything.
- Good:
"PR 2718 has a merge conflict, needs your attention." - Bad: a multi-sentence recap of the whole cycle.
Invocation
say is macOS-only. Wrap it defensively so a caller on another platform (or a machine without
say) never fails because of this notification. Build the message in a shell variable first, then
pass it via quoted expansion — never substitute untrusted text (a PR title, branch name, file
path) directly into the command source, since a stray " could terminate the quote and inject
additional shell content:
message="PR ${pr_number} needs your attention."
command -v say >/dev/null 2>&1 && say "$message" || true
No DATA-vs-instructions treatment is needed here: say only produces local audio output, no
state mutation, so it's exempt from the untrusted-content framing applied to things like
CodeRabbit comment bodies elsewhere in this repo's automation.
Requires .claude/settings.json → "Bash(say:*)" in allow — this skill owns that dependency;
callers don't need their own entry for it.
Related
fix-allskill — example caller, invokes this on every human-attention exit path in its check/fix cycle (scheduled hourly bypr-maintenance-loop, or run directly for a one-shot).test-coverageskill — example caller, invokes this when a test-fix attempt caps out still red or a coverage gap is genuinely untestable.lintskill — example caller, invokes this when a finding needs a broader refactor than patch scope allows.
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 · 63 lines · 58 tokens per session scan A 7db13de6a2ce
say is a skill published in the GitHub repository cloudposse/atmos (1,405 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 689 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
yfm
YAML front matter (YFM) for any markdown article. x-cmd's default is three top-level fields: tags, description, memo. Default borrows the Agent Skills frontmatter shape — see . The yfm module is a helper: x yfm ls / init / lint.
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".
check
Comprehensive rule-based check. Triggered by "/check [target]" to evaluate all source files against project rules and report every violation.
review
Review pull requests or code changes. Triggered by "/review [prlink]" or when user asks to review pending changes.
simplify
Review code for readability, reuse, and simplicity. Triggered by "/simplify" when user wants to refactor complex code, remove duplication, or improve clarity.
scan
Quick greedy scan for critical violations. Triggered by "/scan [target]" to find the top 1-5 most severe issues and stop early.