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/lucasmaher-hash/touch-designer-mcpWrote 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/lucasmaher-hash/touch-designer-mcp/tdmcp-refactor-test-auditor)<a href="https://agentmods.dev/agents/lucasmaher-hash/touch-designer-mcp/tdmcp-refactor-test-auditor"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/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/lucasmaher-hash/touch-designer-mcp/tdmcp-refactor-test-auditor"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/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 | $0.00027 | $0.00201 |
| Sonnet 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 7d 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-refactor-test-auditor — 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-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.
- 7d ago First seen · 49 lines · 54 tokens per session scan A 140e5611064f
tdmcp-refactor-test-auditor is an agent published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 403 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-refactor-test-auditor, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.