Borrowing it
Nothing to install: this file belongs to c9r-io/orchestrator. 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/c9r-io/orchestrator/main/.claude/skills/test-coverage/SKILL.mdgit clone --depth 1 https://github.com/c9r-io/orchestratorWrote 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/c9r-io/orchestrator/test-coverage)<a href="https://agentmods.dev/skills/c9r-io/orchestrator/test-coverage"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/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/c9r-io/orchestrator/test-coverage"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/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.01071 |
| Opus 5.5 | $0.00020 | $0.00428 |
| Sonnet 5.5 | $0.00010 | $0.00214 |
| Haiku 4.5 | $0.00005 | $0.00107 |
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 2mo 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage Skill
Run tests and measure coverage in a project-agnostic way, preferring existing project commands and conventions.
In this repository, measure the Rust workspace from the root and the React/Vite frontend under gui/. For other targets, discover their commands and exclusions first.
Workflow
- Discover the test commands already defined by the project.
- Run unit tests first (fast feedback).
- If coverage is requested: run coverage tooling and identify high-value gaps.
- Improve tests focusing on behavior and critical branches, not raw percentages.
- Re-run tests and coverage to confirm improvement.
Discover Existing Commands
From repo root, look for:
- Backend:
- Rust:
core/Cargo.toml - Workspace commands: root
Cargo.tomland package manifests undercrates/
- Rust:
- Frontend:
gui/package.json
Prefer running existing scripts over inventing new ones.
Backend (Rust, if core/ exists)
Unit Tests
cargo test --workspace
Coverage
Prefer cargo llvm-cov if the project uses it (or has Makefile wrappers). Typical options:
cargo llvm-cov
cargo llvm-cov --html
Why llvm-cov over tarpaulin? tarpaulin has known issues with
#[async_trait]macros (reports dramatically lower coverage for async trait code).cargo-llvm-covuses LLVM's instrumentation and correctly tracks async trait coverage.
If a Makefile defines coverage targets, use those instead:
make coverage
make coverage-html
Notes:
- Coverage exclusions (migrations, generated code, thin wiring) are project-specific. Follow the project's existing exclusions if present.
- Document coverage exclusions so reviewers understand why files are skipped:
| Example Exclusion | Typical Reason |
|---|---|
repository/*.rs |
Thin data mapping layer (ORM-equivalent), no business logic |
main.rs |
Program entry point |
migration/*.rs |
Database migration scripts |
src/index.ts |
Barrel re-export, no logic |
src/types/**/*.ts |
Pure type definitions, no runtime code |
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.
- 2mo ago First seen · 138 lines · 49 tokens per session scan A ad8404337edb
test-coverage is a skill published in the GitHub repository c9r-io/orchestrator (21 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,071 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
schema-check
Check a proposed API or data contract against the current contract, real sample payloads, and a compatibility policy, and gate publication behind a refusable verdict with native digest evidence.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
mcp-builder
Design, build, configure, or debug Model Context Protocol servers for codewhale, including stdio and HTTP/SSE transports.
cw-dogfood
Use when a Codewhale change needs proving in the real product, or when asked to build/install/dogfood the local binaries: stamped release build, atomic install, fresh-shell verification, and the manual QA that gates cannot cover.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.