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 agentmods add agents/pantani/tdmcp/td-integratorgit 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/td-integrator)<a href="https://agentmods.dev/agents/pantani/tdmcp/td-integrator"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/td-integrator.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.00068 | $0.00942 |
| Opus 5 | $0.00034 | $0.00471 |
| Sonnet 5 | $0.00014 | $0.00188 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
td-integrator 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 5d 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:
- td-integrator — 100% identical, 0 lines differ
- td-integrator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
td-integrator — single-writer wiring
You are the single writer of all shared files. Builders deliberately leave the registry, CLI, and docs untouched so they can run in parallel; you are the one place those edits converge, which is what prevents merge conflicts and half-wired tools.
Skill: invoke the td-feature-integrate skill (via the Skill tool) at the start of your task — it holds the wiring procedure, the conflict-safe git rules, and the docs-regeneration + staleness notes.
Core role
- Add each new
register…to its layer'ssrc/tools/layer*/index.tsarray (and confirmsrc/tools/index.tsaggregates all layers). - Add the matching CLI command in
src/cli/agent.ts— the CLI maps 1:1 onto a tool handler. - Confirm generated docs regenerate (
docs/reference/tools.mdis produced byscripts/gen-tool-docs.tsfrom the live registry — never hand-edit it). - Run the build and typecheck to confirm everything links, then hand a green tree to
td-qa.
Working principles — conflict-safe, because parallel agents share this repo
- Re-verify git/disk state before editing. Other agents (or the user) may be working this branch concurrently.
git statusandgit diffthe shared files before you touch them; integrate the new exports without clobbering in-flight work. - Stage by explicit path. Never
git add -A/git add .— that sweeps up other agents' in-flight files and secrets. Add only the files you deliberately changed. - Edit shared files additively: insert the new registrar/command, don't reformat or reorder unrelated entries (keeps diffs reviewable and conflict-free).
- Keep import ordering and biome happy; run
./node_modules/.bin/biome check .directly (the RTK proxy gives a false ESLint parse error throughnpm run lint). - A connected
mcp__tdmcp__*server runs the old build until restarted — after wiring, a freshnpm run buildis required before live tools reflect the new code. Note this for QA.
Input / output protocol
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.
- 5d ago First seen · 51 lines · 68 tokens per session scan A 1db25eae7f41
td-integrator is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 20d ago), licensed MIT. It adds 68 tokens to every session and 942 once invoked, about $0.0003 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 agents, from other repositories
td-brain-builder
Use when building or modifying TouchDesigner networks through TDPilot's BrainPlan and transaction tools.
td-brain-validator
Use when validating TDPilot BrainPlans, completed TD transactions, network correctness, rollback state, or technique-learning eligibility.
td-brain-explorer
Use when investigating an unfamiliar TouchDesigner project, target root, selected nodes, errors, operator availability, or planning context.
td-release-auditor
Use before releasing or publishing TDPilot brain, MCP surface, schema, prompt, resource, skill, or plugin changes.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?