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/test-coverage/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/test-coverage)<a href="https://agentmods.dev/skills/cloudposse/atmos/test-coverage"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/test-coverage/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/test-coverage"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/test-coverage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 67 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
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.00076 | $0.01619 |
| Opus 5.5 | $0.00030 | $0.00648 |
| Sonnet 5.5 | $0.00015 | $0.00324 |
| Haiku 4.5 | $0.00008 | $0.00162 |
Grade A, and why
test-coverage 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage (patch-scoped)
Answers two questions about the current branch's patch vs origin/main: are its tests passing,
and is it adequately covered? Both come from the same scoped test run, so one skill owns both.
Why patch-scoped, not full-suite
The full suite is 349 packages / 1876 test files and takes 45-75 minutes per CI timeouts — running it every hour is not feasible. This skill only ever runs tests for packages containing files this patch touched — it never expands to the other 340+ packages just to go looking for trouble. But once a package is in scope and its run turns up a failure, fix it regardless of whether that specific test or file is what this patch changed: what this loop cares about is the packages it touched actually passing, not whose commit originally broke them.
Running the check
atmos fix coverage [base-ref]
(atmos fix tests [base-ref] is an equivalent alias — same underlying run, reach for it when the
question framing is "are my tests passing" rather than "is my patch covered.") Defaults to
origin/main. This wraps .claude/skills/test-coverage/scripts/patch-test-coverage.sh, which
deliberately does no line-level analysis itself — it just prints a raw bundle (pass/fail status,
raw test output if failed, the coverage profile if passed, and the diff) for the fixing agent to
reason over directly, the same way coderabbit-review reads raw CodeRabbit markdown rather than
us pre-parsing it.
Three outcomes:
STATUS: NO_GO_CHANGES— no touched.gofiles. One-line no-op, done.STATUS: TESTS_FAILING— go to "Fix failing tests" below.STATUS: OK— tests pass; go to "Fix coverage gaps" below.
Fix failing tests (gates coverage — a package with failing tests has meaningless coverage
numbers)
Delegate to Agent subagent_type: "test-coverage-fix", Section A, passing the raw failing-test
output and the list of touched files. The agent classifies each failure as in-scope (the file
lives among this patch's touched files) or pre-existing (it doesn't), but scope only changes
how much diagnosis a fix needs — not whether an attempt is made. What this loop cares about is the
suite passing, full stop; "not this patch's fault" is not a reason to leave something red.
Confirmed for real: a "pre-existing failure" was itself a false positive in the check, not the
code — the patch-scoped go test run had no -timeout override, so Go's 10-minute binary default
tripped on the full (patch-unrelated) ./tests acceptance package under load, panicking on
whichever subtest happened to still be running when the clock ran out. The fix was to the
test-infrastructure itself (patch-test-coverage.sh now passes -timeout 40m, matching
.atmos.d/test.yaml's full-suite convention) — exactly the kind of pre-existing-but-fixable root
cause this agent should resolve rather than just report.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 114 lines · 76 tokens per session scan A 14e8b89eb580
test-coverage is a skill published in the GitHub repository cloudposse/atmos (1,403 stars, last pushed today), licensed Apache-2.0. It adds 76 tokens to every session and 1,619 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
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.