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/hybridlabor-api/bdb-dev-optimized-agent-skillsnpx agentmods add skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-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/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-test-coverage)<a href="https://agentmods.dev/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-test-coverage"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-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/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-test-coverage"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-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.00086 | $0.00653 |
| Opus 5 | $0.00043 | $0.00327 |
| Sonnet 5 | $0.00017 | $0.00131 |
| Haiku 4.5 | $0.00009 | $0.00065 |
Grade A, and why
tdmcp-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 9d 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.
This is a copy
100% identical to tdmcp-test-coverage — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdmcp-test-coverage
Use this skill for coverage-improvement work in this repository. The goal is more tested behavior, not prettier percentages.
Phase 0 - Context
- Read
AGENTS.md,package.json,vitest.config.ts, and the nearest tests. - Run
npm run coverage:harnessunless the user asked for a static-only pass. - Read
_workspace/coverage/latest.md. - Treat the actionable scope as
src/**/*.ts;src/knowledge/data/**is generated reference data and is intentionally excluded.
Phase 1 - Select gaps
Choose one to three independent gaps. Prefer seams where a test can lock a real contract:
- CLI/config: parsing, defaulting, env precedence, diagnostics, and exit behavior.
- Resource/knowledge loaders: URI matching, malformed input, ranking, and stable result shape.
- Tool implementations: Zod defaults, bridge payloads, warnings, and
isErrorpaths using msw. - Server/client boundaries: offline TD behavior, auth forwarding, timeout/retry, event streaming, and transport setup.
Skip generated data, docs-only files, and import-only tests.
Phase 2 - Build tests
For parallel work, spawn tdmcp-coverage-writer agents with one seam each. Give
each writer:
- target file(s) and nearest existing test to mirror;
- behavior to assert;
- expected failure mode or branch to cover;
- exact narrow command to run.
The lead is the single writer for shared config, package scripts, and harness docs. Do not let multiple agents edit the same test file.
Phase 3 - Verify
Run narrow tests first. Then run:
npm run typecheck
npm run build
./node_modules/.bin/biome check .
npm run coverage:harness
npm run validate:recipes
npm run test:bridge
If a gate fails, fix forward. Do not lower coverage thresholds, delete assertions, or exclude executable code to pass.
Phase 4 - Report
Write _workspace/coverage/wave-<date>.md with:
- starting and ending coverage summary;
- tests added and behaviors covered;
- commands run;
- PASS/FAIL/UNVERIFIED buckets;
- next suggested gaps from
_workspace/coverage/latest.md.
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.
- 9d ago First seen · 79 lines · 86 tokens per session scan A f9a7fa65be19
tdmcp-test-coverage is a skill published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 86 tokens to every session and 653 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tdmcp-test-coverage, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
spec-execution
6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.
quality-checklist
Validate implementation quality through custom checklists, scoring against constitution standards, specification coverage, and producing remediation recommendations.
test-enforcement
Automated test validation, coverage checking, and quality metrics with aggressive defaults.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
test-generator
Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on new functions, components, test requests, testing mentions.
testing-strategy
Comprehensive testing skill covering unit, integration, and e2e testing with TDD. Use when writing tests, improving coverage, or setting up testing infrastructure. Keywords: test, TDD, unit test, integration, e2e, coverage, mock, jest, vitest.