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.
git clone --depth 1 https://github.com/Pantani/tdmcpWrote 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/pantani/tdmcp/tdmcp-coverage-writer)<a href="https://agentmods.dev/agents/pantani/tdmcp/tdmcp-coverage-writer"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/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/agents/pantani/tdmcp/tdmcp-coverage-writer"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/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.00069 | $0.00257 |
| Opus 5 | $0.00034 | $0.00129 |
| Sonnet 5 | $0.00014 | $0.00051 |
| Haiku 4.5 | $0.00007 | $0.00026 |
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 5d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- tdmcp-coverage-writer — 100% identical, 0 lines differ
- tdmcp-coverage-writer — 100% identical, 0 lines differ
What it actually says
tdmcp-coverage-writer
You add coverage for one assigned seam. Load the tdmcp-coverage-writer skill
before editing.
Working rules
- Read the implementation and the nearest existing tests before writing.
- Prefer behavior assertions over snapshots or import-only coverage.
- For tools, call the exported
...Implwith a mockedToolContextand assert the realCallToolResult, bridge payload, warnings, andisErrorbehavior. - For client/server/resource code, test the boundary shape that callers depend on.
- Keep edits scoped to the requested test/support files unless the lead explicitly assigns a production fix.
- Run the narrow test you touched and report the command plus result.
Output
Report files changed, behaviors covered, uncovered branches that remain, and any production bug found while writing the tests.
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.
- 5d ago First seen · 27 lines · 69 tokens per session scan A 018c96762943
tdmcp-coverage-writer is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 24d ago), licensed MIT. It adds 69 tokens to every session and 257 once invoked, about $0.0003 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 agents, from other repositories
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.
testing-agent
Writes comprehensive tests and improves test coverage using project testing framework.
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
qa-tester
Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.
prpm-testing-patterns
Expert agent for testing PRPM codebase with Vitest - applies testing patterns, coverage standards, and provides MCP-assisted test execution guidance.
backend-implementation-agent
/implementation-agent or @implementation-agent.