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 hybridlabor-api/bdb-dev-optimized-agent-skills --skill tdmcp-coverage-writergit clone --depth 1 https://github.com/hybridlabor-api/bdb-dev-optimized-agent-skillsWrote 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-coverage-writer)<a href="https://agentmods.dev/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-coverage-writer"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-coverage-writer/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-coverage-writer"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-coverage-writer.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.00051 | $0.00319 |
| Opus 5 | $0.00026 | $0.00160 |
| Sonnet 5 | $0.00010 | $0.00064 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
tdmcp-coverage-writer 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 10d 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-coverage-writer — 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.
What it actually says
tdmcp-coverage-writer
Use this skill when assigned a specific coverage gap.
Workflow
- Read the target implementation and the closest existing tests.
- Identify the behavior or branch that is currently untested.
- Add the smallest test that would fail if that behavior regressed.
- Use existing helpers such as
tests/helpers/tdMock.ts,KnowledgeBase,RecipeLibrary, andsilentLoggerinstead of inventing new scaffolding. - Run the narrow test and fix any real failure.
Assertions to prefer
- Real return text/JSON blocks from
CallToolResult. - Bridge request bodies captured by msw.
- Friendly
isErrorresults instead of thrown handler errors. - CLI stdout/stderr and exit status for user-facing commands.
- Resource URI and payload shape consumed by MCP clients.
Avoid
- Tests that only import a module to mark lines covered.
- Broad snapshots where a specific behavior assertion would do.
- New exclusions in coverage config.
- Rewriting production code unless the test exposes a real bug and the lead asked you to patch it.
Output
Report the changed files, command run, behavior covered, and any remaining branch or live-TD validation that is still unverified.
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.
- 10d ago First seen · 39 lines · 51 tokens per session scan A 335350ecb0df
tdmcp-coverage-writer is a skill published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 51 tokens to every session and 319 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tdmcp-coverage-writer, 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.