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-troubleshootinggit 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-troubleshooting)<a href="https://agentmods.dev/skills/pantani/tdmcp/tdmcp-troubleshooting"><img src="https://agentmods.dev/badge/skills/pantani/tdmcp/tdmcp-troubleshooting/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-troubleshooting"><img src="https://agentmods.dev/badge/skills/pantani/tdmcp/tdmcp-troubleshooting.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.00026 | $0.00350 |
| Opus 5 | $0.00013 | $0.00175 |
| Sonnet 5 | $0.00005 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
tdmcp-troubleshooting 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 8d 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
1 near-identical copy found in the catalogue:
- tdmcp-troubleshooting — 100% identical, 0 lines differ
What it actually says
tdmcp troubleshooting
Use this skill when tdmcp cannot reach TouchDesigner, a structured operation fails, a node cooks with errors, or the observed network differs from the requested result.
Diagnose in layers
- Check local runtime status: package version, configuration source, bridge URL, authentication readiness, and whether the endpoint is reachable.
- If reachable, read bridge info and TouchDesigner build before testing mutating operations.
- Inspect the exact operator path, parameters, connections, cook errors, and preview relevant to the failure.
- Distinguish unsupported endpoint, invalid input, authorization failure, timeout, connection refusal, and TouchDesigner-side error. Do not collapse them into "offline".
- Reproduce with the smallest structured read or mutation. Do not use arbitrary Python merely to bypass a missing first-class operation.
Recovery boundaries
- Do not disable authentication or enable raw execution as a generic repair.
- Do not delete or overwrite artist content to make a health check pass.
- Preserve the configured bridge port; parallel analysis or test bridges must use isolated ports.
- After a repair, repeat the original bounded check and report both the prior failure and current evidence.
- If a check requires a running UI, hardware, pane, or saved project, mark it unverified when that dependency is absent.
Useful evidence includes exact endpoint status, typed error code, operator path, parameter name, TouchDesigner build, and the command or tool result that verified recovery. Redact tokens and project-sensitive content.
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.
- 8d ago First seen · 36 lines · 26 tokens per session scan A 4ee00b10cd90
tdmcp-troubleshooting is a skill published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 26d ago), licensed MIT. It adds 26 tokens to every session and 350 once invoked, about $0.0001 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 skills, from other repositories
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
Concurrency Testing Patterns
Testing concurrent code including race condition detection, deadlock prevention, thread safety verification, and parallel execution correctness.