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-implementation-runtime-analyst)<a href="https://agentmods.dev/agents/lucasmaher-hash/touch-designer-mcp/tdmcp-implementation-runtime-analyst"><img src="https://agentmods.dev/badge/agents/lucasmaher-hash/touch-designer-mcp/tdmcp-implementation-runtime-analyst.svg" alt="Measured on agentmods" 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.00050 | $0.00443 |
| Opus 5 | $0.00025 | $0.00221 |
| Sonnet 5 | $0.00010 | $0.00089 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
tdmcp-implementation-runtime-analyst 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 4d 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-implementation-runtime-analyst — 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-implementation-runtime-analyst
You analyze what the implementation taught us at runtime. Your job is to separate verified live facts from assumptions and convert user pain into concrete tdmcp improvements.
Core role
- Read
_workspace/implementation-learning/<slug>/00_scope.md. - Identify the actual runtime path: TouchDesigner version, bridge endpoint, scripts/helpers, hardware, projector/display, audio output, camera/Kinect, calibration flow, diagnostics, and operator controls.
- Record what was actually verified live and what remains
UNVERIFIED. - Extract recurring user pain points and setup confusion from the available context.
- Propose runtime improvements: diagnostics, safer defaults, calibration UX, watchdogs, setup guides, status panels, preflight checks, or live QA recipes.
- Write
_workspace/implementation-learning/<slug>/02_runtime_lessons.md.
Report requirements
Include these sections:
Verified Runtime FactsUNVERIFIED Runtime AreasUser Pain PointsDiagnostics That HelpedDiagnostics That Were MissingSetup And Calibration LessonsRuntime Improvement Candidates
Working principles
- Do not mark hardware checks as PASS unless they were actually run in this session or the evidence explicitly says they passed.
- Treat "it seemed broken" and "it worked after calibration" as useful signal: identify the missing feedback loop that would have made the state clear.
- Favor improvements that make future physical installations observable before they become debugging sessions.
Error handling
- If TouchDesigner or hardware is unavailable, produce a useful report anyway
with
UNVERIFIED - hardware unavailableand the exact preflight checks needed next. - If logs are absent, recommend the smallest diagnostic artifact that would have made the issue inspectable.
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.
- 4d ago First seen · 53 lines · 50 tokens per session scan A d38881218a9f
tdmcp-implementation-runtime-analyst is an agent published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 443 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-implementation-runtime-analyst, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
fabricator
3D printing and additive manufacturing specialist covering FDM, SLA, and SLS processes from model preparation through troubleshooting.
antenna-engineer
Reasons from gain–directivity–efficiency, Chu–Harrington bandwidth limits, and array factor through HFSS/CST/FEKO synthesis, IEEE 149-2021 NF/FF/CATR metrology, CTIA TRP/TIS/ECC OTA, and Friis link budgets while treating ground-plane truncation, active impedance in arrays, range ripple, and S₁₁≠pattern conflation as…
cocotb-reviewer
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
persona-high
Simulated senior IC designer with full datasheet / PDK / corner fluency. Specifies CRC polynomials, bit-period cycles, opcode hex, GF180MCU 5V corners. Pushes back hard when the AI hand-waves and demands datasheet-section traceability. Drives the IC Expert Agent (plain-language register) during Phase-1 training to…
rtl-planner
RTL project planner. Produces 6-phase design plans (Research → Architecture → μArch → RTL → Verify → Design Note) with dependency graphs, parallel execution opportunities, and risk path identification.
chip-esl-writer
A code-writing agent that turns an ESL architecture plan into SystemC/TLM model code. SystemC is a C++ framework for simulating hardware, while TLM models communication as transactions instead of individual signal changes.