Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Nordic-AI/production-readiness-skillsnpx agentmods add skills/nordic-ai/production-readiness-skills/test-coverageWrote 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/nordic-ai/production-readiness-skills/test-coverage)<a href="https://agentmods.dev/skills/nordic-ai/production-readiness-skills/test-coverage"><img src="https://agentmods.dev/badge/skills/nordic-ai/production-readiness-skills/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/nordic-ai/production-readiness-skills/test-coverage"><img src="https://agentmods.dev/badge/skills/nordic-ai/production-readiness-skills/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.00110 | $0.03613 |
| Opus 5 | $0.00055 | $0.01806 |
| Sonnet 5 | $0.00022 | $0.00723 |
| Haiku 4.5 | $0.00011 | $0.00361 |
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 11d 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage Audit
You review the adequacy of automated testing. Coverage percentage is necessary but not sufficient — you also check what is covered, how it's covered, and whether the tests actually assert meaningful behavior.
Inputs
From orchestrator: scope_tier, stack_summary, gitnexus_indexed, and critical-path map (entry points, HTTP handlers, workers, jobs).
Mode detection
- Plan mode — produce coverage report with gap list.
- Edit mode — after report, offer to generate missing tests. Generate test scaffolds with meaningful assertions, not just
expect(thing).toBeDefined().
Thresholds by tier
| Tier | Line | Branch | Integration tests | Stress/load | Property-based |
|---|---|---|---|---|---|
| prototype | advisory (aim 60%+) | advisory | optional | not required | optional |
| team | 90% required | 90% required | required for every critical path | basic smoke load (happy-path + 2× expected throughput) | recommended |
| scalable | 90% required | 90% required | required + contract tests between services | realistic stress + chaos + soak (24h+) | required for serialization / parsing / state machines |
"Critical path" = any code path that handles: authentication, authorization, payments, PII reads/writes, external data writes, anything invoked by a scheduled job or message consumer, anything with regulatory relevance.
Step 1 — discover the test setup
- Detect the test framework(s):
- JS/TS:
jest,vitest,mocha,playwright,cypress,@testing-library/*,ava. - Python:
pytest,unittest,hypothesis(property),locust(load). - Go: built-in
testing,testify,gomock,vegeta/k6for load. - Java/Kotlin:
junit5,testng,mockito,gatling. - Rust: built-in,
proptest,criterion. - .NET:
xunit,nunit,mstest. - Ruby:
rspec,minitest.
- JS/TS:
- Read the test config (
jest.config.*,pytest.ini,pyproject.toml [tool.pytest.ini_options],go.mod, etc.) to understand: coverage thresholds, excluded paths, test patterns. - Detect CI invocation — does CI actually run tests? Does it enforce a coverage threshold? Grep
.github/workflows/,.gitlab-ci.yml,.circleci/, etc. - Inventory test directories: unit vs integration vs e2e vs load. Count files, count test cases.
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.
- 11d ago First seen · 328 lines · 110 tokens per session scan A 298c1613f223
test-coverage is a skill published in the GitHub repository Nordic-AI/production-readiness-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 110 tokens to every session and 3,613 once invoked, about $0.0006 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-31.
Other skills, from other repositories
req-to-test
Generates comprehensive test scenarios from requirements including BDD/Gherkin scenarios, unit tests, integration tests, and end-to-end test cases. Use when converting requirements, user stories, or specifications into testable scenarios with full coverage including happy paths, error cases, edge cases, and boundary…
test-strategy
Use when deciding what to test and at which level. Covers the test pyramid, what belongs in unit versus integration versus end-to-end tests, coverage as a signal rather than a target, and eliminating flakiness.
test-levels
This skill explains the 3 test levels (Unit, Integration, E2E) using the "Building a Car" analogy and provides guidance on when to use each type. Includes project-specific Playwright examples.
writing-tests
Write unit, integration, and E2E tests that follow the testing pyramid, the Arrange-Act-Assert pattern, the shouldXwhenY naming convention, and meet a 75% (target 80%) branch coverage gate per supported OS. Use when the user asks to write tests, add coverage, build a test suite, fix flaky tests, or verify a feature…
test-strategy-document
Create a production-ready Testing Strategy and QA Execution Plan. Covers testing levels (unit, integration, E2E, performance), mocking boundaries, test environment matrix, code coverage thresholds, and automated CI pipeline runsheets. Use when establishing a QA framework for a new system or feature set.
wp-plugin-testing
Use when writing or setting up tests for a WordPress plugin — PHPUnit integration tests using WPUnitTestCase with the WP test suite (bin/install-wp-tests.sh, phpunit.xml.dist, tests/bootstrap.php), unit tests with Brain Monkey (when() / expect() / Mockery) or WPMock, test factories (factory()->post->create()…