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 atretyak1985/swarmery --skill test-coveragegit clone --depth 1 https://github.com/atretyak1985/swarmeryWrote 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/atretyak1985/swarmery/test-coverage)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/test-coverage"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/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/atretyak1985/swarmery/test-coverage"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/test-coverage.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.00826 |
| Opus 5.5 | $0.00020 | $0.00330 |
| Sonnet 5.5 | $0.00010 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00083 |
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Analyze test coverage gaps across the project's repositories (project.json → repos) by mapping source files to test files, identifying untested modules and public functions, classifying risk, and suggesting what to test. This skill identifies what to test and owns the authoritative coverage-target table; the testing skill provides how — run this first, then hand off.
Rules (never violate)
- Read-only: never create or edit test files during gap analysis.
- Exclude generated files, type declarations, build outputs, and test fixtures from the "untested" count.
- Every untested module gets a risk classification (High/Medium/Low) with rationale.
- Label the gap number an estimate — file/function mapping, not tool-measured line coverage.
- Never run the full suite (
make test-all) — gap analysis needs no execution. - Report stays within 200 lines; over 50 gaps → group by directory, detail the top 10 by risk.
Resources
- Read
resources/gap-analysis-procedure.mdwhen running the analysis: the 6-step procedure (scope, inventory, mapping, gaps, suggested cases, target comparison) with checkpoints, the report template, the authoritative coverage-target table, self-check, mistakes, escalation, and failure modes.
How to use
What it does
Finds the holes in your test suite without touching a single file: it walks a repository or module, matches every source file to its expected test file, and reports what has no coverage — plus which exports inside tested files still lack cases. Each gap carries a risk level, a suggested test file path following your conventions, and 3–5 cases worth writing.
When to use it
- "What's untested?" needs an answer grounded in the actual file tree.
- Before a release, confirming high-risk paths (auth, streaming, mutating routes) have tests.
- After new modules land, checking whether tests landed too; prioritizing limited testing time.
Not for: writing/running/debugging tests (testing), real line/branch percentages (run --coverage directly), code complexity (code-quality/code-standards), or CI test jobs (the project's infra pack skills).
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 · 66 lines · 49 tokens per session scan A e786027c0a29
test-coverage is a skill published in the GitHub repository atretyak1985/swarmery (7 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 826 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-09-03.
Other skills, from other repositories
verify
Verify phase — evidence-based validation with sentinel dispatch and pass/fail scorecard.
k8s-sidecar-testing
Test the nat464-sidecar demo topology in a selected Kubernetes test namespace, verify IPv6 translation paths, and compare HTTP latency. Includes optional disposable Multipass/k3s setup.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
typescript-providers
Implement, modify, test, or document TypeScript provider packages under ts/packages/providers, including framework adapters for OpenAI, Anthropic, Google, LangChain, Mastra, Vercel, LlamaIndex, Cloudflare, Claude Agent SDK, and TypeSafe. Use for provider-specific TS work; do not use for core-only changes.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
adk-setup
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test run. Runs only when explicitly requested, never on its own. Use when asked to set up, bootstrap, or repair a development…