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 Pantani/tdmcp --skill tdmcp-quality-auditgit 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/skills/pantani/tdmcp/tdmcp-quality-audit)<a href="https://agentmods.dev/skills/pantani/tdmcp/tdmcp-quality-audit"><img src="https://agentmods.dev/badge/skills/pantani/tdmcp/tdmcp-quality-audit/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/pantani/tdmcp/tdmcp-quality-audit"><img src="https://agentmods.dev/badge/skills/pantani/tdmcp/tdmcp-quality-audit.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.00111 | $0.01611 |
| Opus 5 | $0.00056 | $0.00805 |
| Sonnet 5 | $0.00022 | $0.00322 |
| Haiku 4.5 | $0.00011 | $0.00161 |
Grade A, and why
tdmcp-quality-audit 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 11d 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-quality-audit — 100% identical, 0 lines differ
- tdmcp-quality-audit — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdmcp-quality-audit
Use this skill for broad repository quality campaigns. It coordinates existing
tdmcp specialists instead of replacing them: tdmcp-test-coverage handles focused
coverage waves, and td-feature-qa handles tool/CLI/docs/bridge boundary QA.
Execution mode: hybrid fan-out/fan-in
This environment runs coordinated sub-agents rather than TeamCreate. Spawn the
independent auditors in parallel, then fan their reports into one lead-owned plan.
Implementation happens in small waves after QA verifies the findings.
Agent roster
| Agent | Focus | Output |
|---|---|---|
tdmcp-quality-audit-lead |
scope, orchestration, shared edits, wave plan | _workspace/quality-audit/00_scope.md, 05_plan.md |
tdmcp-command-auditor |
scripts, Makefile, CI, CLI command health | _workspace/quality-audit/01_commands.md |
tdmcp-security-auditor |
trust boundaries, raw Python, env redaction, package safety | _workspace/quality-audit/02_security.md |
tdmcp-ux-flow-auditor |
first-run, docs-to-command parity, CLI help/errors | _workspace/quality-audit/03_usability.md |
tdmcp-refactor-test-auditor |
coverage gaps, weak tests, complexity, refactor seams | _workspace/quality-audit/04_refactor_tests.md |
tdmcp-quality-qa |
verifies evidence and first patch wave | _workspace/quality-audit/06_qa.md |
Phase 0 - Context check
- Read
AGENTS.md,CLAUDE.md,package.json,Makefile,.github/workflows/*.yml,vitest.config.ts, and existing_workspace/quality-audit/reports. - Decide run mode:
- no quality workspace: fresh audit;
- existing reports + user asks to continue/fix/re-run: partial re-run;
- new broad request: archive prior reports under
_workspace/quality-audit/archive/<timestamp>/before a fresh audit.
- Check git status. Do not revert unrelated user changes.
Phase 1 - Scope and command policy
Create _workspace/quality-audit/00_scope.md with:
- requested scope;
- current branch and dirty-state summary;
- commands that are safe one-shot;
- commands requiring timeout;
- commands requiring TouchDesigner, hardware, network, or credentials;
- commands that are publish/destructive and must not run without explicit user approval.
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.
- 11d ago First seen · 152 lines · 111 tokens per session scan A 764e60ff0947
tdmcp-quality-audit is a skill published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 26d ago), licensed MIT. It adds 111 tokens to every session and 1,611 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
gentle-ai-bench
Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
remove-ai-slops
Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.
testing-anti-patterns
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or…
eval-leakage-audit
Audits whether a verification (eval/metric/experiment/holdout) actually secures independent external ground truth, or whether the designer, the model, and the scorer are just confirming each other in a circle — via a 21-pattern taxonomy. Read-only. Use before trusting any 'how we'll know it worked' — A/B tests…
coverage
Compute code coverage for active track or module. Targets 95%+ coverage with report and justification for uncovered lines. Complements TDD workflow.