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/MauricioPerera/KDDnpx agentmods add skills/mauricioperera/kdd/kdd-test-coverage-scanWrote 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/mauricioperera/kdd/kdd-test-coverage-scan)<a href="https://agentmods.dev/skills/mauricioperera/kdd/kdd-test-coverage-scan"><img src="https://agentmods.dev/badge/skills/mauricioperera/kdd/kdd-test-coverage-scan/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/mauricioperera/kdd/kdd-test-coverage-scan"><img src="https://agentmods.dev/badge/skills/mauricioperera/kdd/kdd-test-coverage-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00167 | $0.01899 |
| Opus 5 | $0.00084 | $0.00949 |
| Sonnet 5 | $0.00033 | $0.00380 |
| Haiku 4.5 | $0.00017 | $0.00190 |
Grade A, and why
kdd-test-coverage-scan 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 12d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage Scan (Capa 3 de KDD -- gaps de cobertura)
Produce hallazgos de gaps de cobertura de tests en el formato de contrato que audita la Capa 3 de KDD. Esta skill NO es el gate -- es la parte creativa/no determinista (identificar rutas criticas, cruzarlas con reportes de cobertura y con el historial de incidentes, juzgar el impacto de cada gap) que el gate despues valida. Distincion central: el agente decide QUE es un gap de cobertura; el gate solo audita que el artefacto sellado cumpla forma y politica de calidad de datos.
Lee esto primero: la frontera con CCDD
Antes de usar esta skill, confirma que lo que buscas NO ya lo cubre
CCDD. CCDD (Nivel 1 obligatorio, sin activar nada) exige que todo
task contract en knowledge/contracts/ tenga:
- un oraculo de tests congelado (
tests_sha256en el frontmatter, gateado porvalidate_contracts.py); - su
test_commanden verde (gateado porvalidate_test_commands.py).
Si tu pregunta es "¿esta funcion que se implemento via un task contract tiene tests que pasan?", esa respuesta ya existe -- no necesitas esta skill ni el dominio que gobierna.
Esta skill sirve para lo que CCDD deliberadamente NO cubre:
- Codigo que nunca paso por un task contract. La mayoria de un proyecto real, sobre todo si KDD se adopto sobre un codebase preexistente.
- Gaps de TIPO de cobertura, no de presencia. Un
test_commanden verde certifica que ESOS tests pasan, no que cubran el caso de error, la condicion de carrera, o el camino que revelo un incidente real. - Test de regresion faltante tras un bug real ya corregido.
Ver la seccion completa de frontera en
knowledge/data_models/test_coverage_findings.md.
Cuando usarla
El usuario pide auditar si las rutas criticas de un sistema (dentro o fuera de contratos CCDD) tienen el tipo de cobertura de tests que hace falta, y quiere el resultado gobernado por KDD (versionable, gateado en CI, con politica declarativa), no un reporte suelto en prosa.
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.
- 12d ago First seen · 163 lines · 167 tokens per session scan A ace382e93073
kdd-test-coverage-scan is a skill published in the GitHub repository MauricioPerera/KDD (8 stars, last pushed 3d ago), licensed MIT. It adds 167 tokens to every session and 1,899 once invoked, about $0.0008 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
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
react-testing
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
python-testing
Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization. Use when writing or improving Python tests.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.