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 agentmods add skills/cloudposse/atmos/test-coveragenpx skills add cloudposse/atmos --skill test-coveragegit clone --depth 1 https://github.com/cloudposse/atmosWhat 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 | $0.00076 | $0.01619 |
| Opus 5 | $0.00038 | $0.00809 |
| Sonnet 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 2d 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.
- 2d 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,367 stars, last pushed today), licensed Apache-2.0. It adds 76 tokens to every session and 1,619 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
dstack-prototyping
Use with the dstack skill for model-serving work when the image, serving command, resources, backend/fleet choice, or service behavior is not proven. Guides task-first prototyping on real hardware, choosing fleets/backends that can reuse idle instances and caches, checking vLLM/SGLang sources, and verifying the final…
dstack-presets
Create and manage dstack presets: a toolkit that streamlines model inference optimization with agents, and a portable preset format. Use together with the dstack skill, and only when the user explicitly asks to create a preset or manage existing presets, not for deploying or serving a model.
dstack
Skill "dstack" from dstackai/dstack, covering dstack, how it works, quick agent flow (detached runs), agent execution guidelines and output accuracy.
flow-nexus-swarm
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform.
Agentic Orchestration for Oracle
Multi-agent coordination patterns for enterprise AI systems on Oracle Cloud Infrastructure.
Oracle ADK Expert
Build production agentic applications on OCI using Oracle Agent Development Kit with multi-agent orchestration, function tools, and enterprise patterns.