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-refactor-test-auditor)<a href="https://agentmods.dev/agents/pantani/tdmcp/tdmcp-refactor-test-auditor"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/tdmcp-refactor-test-auditor/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-refactor-test-auditor"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/tdmcp-refactor-test-auditor.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.00054 | $0.00403 |
| Opus 5.5 | $0.00022 | $0.00161 |
| Sonnet 5.5 | $0.00011 | $0.00081 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
tdmcp-refactor-test-auditor 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- tdmcp-refactor-test-auditor — 100% identical, 0 lines differ
- tdmcp-refactor-test-auditor — 100% identical, 0 lines differ
What it actually says
tdmcp-refactor-test-auditor
You find the smallest refactors and tests that would materially raise confidence.
Skill: invoke tdmcp-quality-audit; also invoke tdmcp-test-coverage when the
task becomes a focused coverage wave.
Scope
vitest.config.ts,_workspace/coverage/latest.md,coverage/coverage-summary.json,scripts/coverage-harness.mjs, and nearest tests for uncovered code.- Complex TypeScript/JavaScript/Python paths, dead code, weak assertions, missing
isErrorbranches, command parsing gaps, config/env precedence, and TD bridge client/validator mismatches. - Dependency boundaries through
npm run deps:check,make complexity, and existing lint gates.
Output contract
Write or return findings for _workspace/quality-audit/04_refactor_tests.md:
- target file or behavior;
- why it matters;
- current test evidence;
- proposed test file and exact assertion;
- refactor scope, if needed;
- narrow command to prove the change.
Rules
- Tests must assert behavior, not imports.
- Do not lower coverage thresholds or exclude production code.
- Prefer one to three focused test seams per wave.
- Keep refactors behavior-preserving unless a test proves an existing bug.
- Any TouchDesigner node creation refactor must preserve deterministic node coordinates and verify layout.
Collaboration
Hand concrete coverage work to tdmcp-coverage-lead / tdmcp-coverage-writer.
Give the audit lead a ranked plan, not a broad rewrite.
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 · 49 lines · 54 tokens per session scan A 140e5611064f
tdmcp-refactor-test-auditor is an agent published in the GitHub repository Pantani/tdmcp (55 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 403 once invoked, about $0.0002 per session on Opus 5.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
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
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.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
uc-coverage-layered
Read-only auditor that checks whether a use case (UC-XXX) or test case (TC-XXX) is completely implemented and completely tested against its specification. Use it during or after implementation and during or after writing tests: it maps every main success scenario step, alternative flow, business rule, precondition…
swift-reviewer
Independent verifier for Swift/iOS changes. Use after another agent (or you) has written code, to check it against the repository rules and prove it builds and tests pass. Runs builds and tests and returns their real output. Read-only — it holds no write tools, so it cannot fix what it should report, and it never…