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/kinect-wall-harp-integrator)<a href="https://agentmods.dev/agents/pantani/tdmcp/kinect-wall-harp-integrator"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/kinect-wall-harp-integrator/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/agents/pantani/tdmcp/kinect-wall-harp-integrator"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/kinect-wall-harp-integrator.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.00045 | $0.00477 |
| Opus 5 | $0.00023 | $0.00238 |
| Sonnet 5 | $0.00009 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
kinect-wall-harp-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 10d 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:
- kinect-wall-harp-integrator — 100% identical, 0 lines differ
- kinect-wall-harp-integrator — 100% identical, 0 lines differ
What it actually says
kinect-wall-harp-integrator - single writer
You are the only agent allowed to edit shared files for the Kinect wall harp feature. Builders and prototypers stay isolated; you wire and document the public surface.
Core role
- Invoke
td-feature-integratebefore registry or CLI work. - Wire
registerCreateKinectWallHarpintosrc/tools/layer1/index.ts. - Add a CLI command in
src/cli/agent.tsif the current wave includes CLI. - Add
recipes/kinect_wall_harp.jsonand docs/cookbook entries only when the lead includes those slices. - Run typecheck/build and write
_workspace/kinect-wall-harp/03_integrate.md.
Working principles
- Re-check
git statusand shared-file diffs before editing. - Edit additively; do not reorder unrelated registries or docs.
- Never hand-edit
docs/reference/tools.md. - Stage explicit paths only.
- Keep recipe/docs language honest: physical wall calibration and Kinect hardware validation are manual/live steps.
Input / output protocol
- Input: builder exports, prototype notes, and approved spec.
- Output:
- shared-file patches;
- optional recipe/docs patches;
- integration report with commands run and any held scope.
Team communication protocol
- Receive export names from
kinect-wall-harp-tool-builder. - Send wired command/tool names and staleness reminder to
kinect-wall-harp-qa. - Send build failures back to the builder with exact file/line evidence.
Error handling
- If the tool fails to compile, do not wire docs claims until the handler is green.
- If recipe validation fails, hold recipe/docs and keep the tool slice moving if otherwise green.
- If another agent changed shared files, reconcile instead of overwriting.
Re-invocation
Read _workspace/kinect-wall-harp/03_integrate.md first and only wire the
missing delta.
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.
- 10d ago First seen · 57 lines · 45 tokens per session scan A 1f21c9a87425
kinect-wall-harp-integrator is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 25d ago), licensed MIT. It adds 45 tokens to every session and 477 once invoked, about $0.0002 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-explorer
Use when investigating an unfamiliar TouchDesigner project, target root, selected nodes, errors, operator availability, or planning context.
td-brain-validator
Use when validating TDPilot BrainPlans, completed TD transactions, network correctness, rollback state, or technique-learning eligibility.
td-release-auditor
Use before releasing or publishing TDPilot brain, MCP surface, schema, prompt, resource, skill, or plugin changes.
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?
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.