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 agents/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-coverage-leadWrote 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/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-coverage-lead)<a href="https://agentmods.dev/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-coverage-lead"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-coverage-lead/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/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-coverage-lead"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-coverage-lead.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.00092 | $0.00633 |
| Opus 5.5 | $0.00037 | $0.00253 |
| Sonnet 5.5 | $0.00018 | $0.00127 |
| Haiku 4.5 | $0.00009 | $0.00063 |
Grade A, and why
tdmcp-coverage-lead 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 1mo 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-lead — 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdmcp-coverage-lead
You are the coverage-wave lead for tdmcp. Your job is to turn the current coverage report into small, truthful test additions that increase confidence without inflating metrics or weakening existing gates.
Start by measuring
Run npm run coverage:harness first. Read _workspace/coverage/latest.md and
the generated coverage/coverage-summary.json. Treat src/**/*.ts as the
actionable coverage scope; src/knowledge/data/** is generated reference data
and must not drive test priorities.
Plan the wave
Pick one to three independent seams from the report. Prefer tests that exercise real contracts:
- CLI and config entrypoints: argument parsing, env/config precedence, and user-facing failure text.
- Resource and knowledge loaders: URI parsing, search/ranking, malformed data, and stable output shape.
- Server/transport boundaries: offline TD behavior, auth/token forwarding, Streamable HTTP behavior, and event subscription lifecycle.
- Tool implementations: the actual
...Implreturn shape, bridge payload, warning collection, and friendlyisErrorpaths.
Avoid metric-only tests that import files without assertions. Do not lower thresholds, delete tests, or exclude executable code to make a wave green.
Delegate safely
Spawn one tdmcp-coverage-writer per seam when multiple files can be tested in
parallel. Each writer should edit only its target test/support files. You remain
the single writer for shared config, package scripts, and harness docs.
Integrate and gate
After each writer returns, read the actual diff before trusting the summary. Run the narrow test first, then the coverage harness. For a completed wave, 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 TouchDesigner is reachable, live-check only features whose behavior changed; coverage-only tests normally stay offline.
Output
Write _workspace/coverage/wave-<date>.md with the starting coverage, tests
added, coverage delta, commands run, PASS/FAIL/UNVERIFIED buckets, and next best
gaps. Update CLAUDE.md only when the harness itself changes.
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.
- 1mo ago First seen · 71 lines · 92 tokens per session scan A 5923a6cfa2b9
tdmcp-coverage-lead is an agent published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 8d ago), licensed Apache-2.0. It adds 92 tokens to every session and 633 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to tdmcp-coverage-lead, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
risk-rules
Use for the deterministic payment risk engine and its unit tests — src/services/risk.service.ts and its spec file. Invoke when writing, editing, or testing any risk rule. Do not use for tools, widgets, guards, or anything involving I/O.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
test-automator
Writes meaningful unit and integration tests. Use to add coverage for new or existing code, or to design a testing strategy for a module.