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 paruff/uFawkesAI --skill test-coverage-validationgit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/test-coverage-validation)<a href="https://agentmods.dev/skills/paruff/ufawkesai/test-coverage-validation"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/test-coverage-validation/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/paruff/ufawkesai/test-coverage-validation"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/test-coverage-validation.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.00024 | $0.00644 |
| Opus 5 | $0.00012 | $0.00322 |
| Sonnet 5 | $0.00005 | $0.00129 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
test-coverage-validation 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 8d 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.
Skill: Test Coverage Validation
Load trigger:
"load test-coverage-validation skill"> DORA: Cap 5 (Small Batches / Shift Left on Quality) Token cost: Low
Purpose
Validate that test coverage meets platform thresholds.
Responsibilities
- Analyze coverage data from test runs
- Validate coverage against thresholds
- Identify untested or under-tested areas
- Produce coverage report
Inputs
- Coverage data (from unit/integration test runs)
- Governance rules (threshold requirements)
Outputs
coverage-report.jsoncoverage-summary.md
Thresholds
Default Thresholds
| Metric | Minimum | Target |
|---|---|---|
| Line coverage | 80% | 90% |
| Branch coverage | 75% | 85% |
| Function coverage | 85% | 95% |
| Statement coverage | 80% | 90% |
Severity Classification
| Gap | Severity |
|---|---|
| Critical module below 60% | HIGH |
| Module below threshold | MEDIUM |
| New code below threshold | HIGH |
| Existing code below threshold | LOW |
Validation Rules
Coverage Analysis
- Coverage data parsed and normalized
- Per-file coverage calculated
- Per-module coverage calculated
- Overall coverage calculated
Threshold Check
- Line coverage ≥ threshold
- Branch coverage ≥ threshold
- Function coverage ≥ threshold
- No critical module below 60%
Gap Identification
- Files with 0% coverage flagged
- Files below threshold flagged
- Critical paths with low coverage flagged
- Untested error paths flagged
Output Format
{
"skill": "test-coverage-validation",
"status": "pass | fail",
"overall": {
"line": 87.5,
"branch": 79.2,
"function": 92.1,
"statement": 86.3
},
"thresholds": {
"line": 80,
"branch": 75,
"function": 85,
"statement": 80
},
"gaps": [
{
"file": "src/services/payment.ts",
"line_coverage": 45.2,
"severity": "HIGH",
"reason": "Critical module below 60%"
}
]
}
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.
- 8d ago First seen · 114 lines · 24 tokens per session scan A 4c76836cc4ce
test-coverage-validation is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 19d ago), licensed MIT. It adds 24 tokens to every session and 644 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
template-formal
Strongly-typed multiagent ant-robot colony exemplar — ADTs, session-typed protocols, affine-discipline resource handles, storage-as-functor framing, Active-Inference-flavored decision loop, mypy-as-oracle negative controls.
template-reproducibility-audit
Deterministic reproducibility audit — fixed seeds, regenerate-from-clean, double-run diff before Zenodo/arXiv/release. USE WHEN outputs drift between runs, "worked on my machine", need regenerate-from-clean proof, or pre-release reproducibility check — even without naming docs/prompts.
template-test-creation
Create pytest suites under the no-mocks policy — real data, temp files, subprocess, pytest-httpserver. USE WHEN adding tests, raising coverage, testing new src/ module, or user forbids mocks.
infrastructure-benchmark
Deterministic benchmark harnesses for public template exemplars. Use when scoring generated project outputs against benchmark manifests, refreshing the default template smoke manifest, checking publication-readiness rubrics, or adding bounded no-network readiness checks for public template outputs.
infrastructure-sia
Skill for the Self-Improvement Agent (SIA) harness contract. Use when validating task public/private layouts, generation artifact trees, evaluation runners, fixture replay loops, or opt-in live Meta→Target→Feedback cycles in template projects.
template-sia
SIA (Self-Improvement Agent) harness exemplar — Meta/Target/Feedback loops, public/private splits, fixture replay, fail-closed validation.