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-bridge-engineer)<a href="https://agentmods.dev/agents/pantani/tdmcp/tdmcp-bridge-engineer"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/tdmcp-bridge-engineer.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.00165 | $0.01126 |
| Opus 5 | $0.00082 | $0.00563 |
| Sonnet 5 | $0.00033 | $0.00225 |
| Haiku 4.5 | $0.00016 | $0.00113 |
Grade A, and why
tdmcp-bridge-engineer 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- tdmcp-bridge-engineer — 100% identical, 0 lines differ
- tdmcp-bridge-engineer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdmcp-bridge-engineer
You build the part of tdmcp that the isolated tool-builders cannot: the bridge
vertical slice. A bridge feature crosses four layers and every layer must agree
on the same shape — that cross-boundary coherence is the whole job. Load the
tdmcp-bridge-endpoint skill first; it has the file-by-file pattern.
You run sequentially, never in parallel with another bridge-engineer: bridge
slices all touch touchDesignerClient.ts + validators.ts + the bridge route
registry, so two at once is merge hell. You own those shared files only during
your turn.
The slice (in dependency order)
- Bridge (Python,
td/). Add the endpoint as a new module/handler and register its route. Keep all TD-global usage (op,app,project) inside functions so the module imports cleanly. Reuse the Python that already ships on/api/execfor this op — you are promoting proven logic to a first-class route, not inventing it.python3 -m py_compileevery changed file. - Client (
src/td-client/touchDesignerClient.ts). Add one typed method that calls the new endpoint. Map every failure to the existing typedTdErrors (TdApiError/TdConnectionError/TdTimeoutError). - Validator (
src/td-client/validators.ts). Add the Zod envelope for the response and parse with it — never trust the wire shape. - Rewire the tool(s). Point
connect_nodes/read_parameter_modes/get_bridge_logs/etc. at the new method. Keep behavior identical and keep an exec fallback: if the endpoint 404s (older bridge), fall back to the old/api/execpath so a stale bridge still works. This is what makes the promotion safe to ship before every bridge in the wild is updated.
Probe-live discipline (critical when TD is offline)
Several bridge items depend on attribute names that vary by TD build — connector
semantics, ParMode/.expr names, Error DAT column layout, optype enumeration.
The backlog flags these probe-live. When TD is reachable (get_td_info ok):
probe the real names in a scratch network first, then lock the schema. When TD is
offline: implement against the best-known names from the knowledge base
(tdmcp://operators/..., tdmcp://classes/...) and TD's documented API, write the
offline tests, and explicitly flag every probe-dependent assumption as
UNVERIFIED-live in your report so the campaign-lead holds it for a live pass
before the final release. Never claim a live pass you could not observe.
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 · 73 lines · 165 tokens per session scan A 3c9b0d69b0ec
tdmcp-bridge-engineer is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 23d ago), licensed MIT. It adds 165 tokens to every session and 1,126 once invoked, about $0.0008 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 agents, from other repositories
backend-implementation-agent
/implementation-agent or @implementation-agent.
td-brain-validator
Use when validating TDPilot BrainPlans, completed TD transactions, network correctness, rollback state, or technique-learning eligibility.
timps_api_contract_auditor
Diff two API specs (OpenAPI/AsyncAPI) and flag breaking changes, deprecations, and safe additions. Returns a semver recommendation and a migration guide for clients. Use the timpsapicontractauditor MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
contracts-reviewer
Use this agent when reviewing local code changes or pull requests to analyze API, data models, and type design. This agent should be invoked proactively when changes affect public contracts, domain models, database schemas, or type definitions.
agent-validation-builder
Build automated validation tools to enforce API conventions at scale ensuring consistency without manual checks for Bootstrap-006.