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-kinect-wall-harpgit 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-kinect-wall-harp)<a href="https://agentmods.dev/skills/pantani/tdmcp/tdmcp-kinect-wall-harp"><img src="https://agentmods.dev/badge/skills/pantani/tdmcp/tdmcp-kinect-wall-harp/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-kinect-wall-harp"><img src="https://agentmods.dev/badge/skills/pantani/tdmcp/tdmcp-kinect-wall-harp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00097 | $0.01988 |
| Opus 5 | $0.00048 | $0.00994 |
| Sonnet 5 | $0.00019 | $0.00398 |
| Haiku 4.5 | $0.00010 | $0.00199 |
Grade A, and why
tdmcp-kinect-wall-harp 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 12d 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-kinect-wall-harp — 100% identical, 0 lines differ
- tdmcp-kinect-wall-harp — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdmcp-kinect-wall-harp - implementation orchestrator
Coordinate the dedicated team for the approved Kinect wall harp prototype. This skill specializes the generic tdmcp pipeline for a physical Kinect v2 + projector wall instrument where FreenectTD depth behavior, manual calibration, two-hand blob tracking, internal audio, and honest live validation all matter.
Execution mode
This repo documents that the current environment runs teams as coordinated
sub-agents rather than TeamCreate. Use a hybrid sub-agent workflow:
| Phase | Mode | Reason |
|---|---|---|
| Plan | local lead or kinect-wall-harp-lead |
keep scope tied to the approved spec and wall setup. |
| Prototype + tool build | parallel sub-agents when write scopes are disjoint | live TD prototype and isolated tool file can advance separately. |
| Integrate/docs | single-writer sub-agent | registries, CLI, recipes, and docs are shared files. |
| QA/fix loop | sub-agent fan-in | QA routes precise defects to the owner; live hardware gets PASS / UNVERIFIED accounting. |
All spawned agents use the inherited model unless the user explicitly asks for a different one.
Agent roster
| Agent | Role | Skills | Output |
|---|---|---|---|
kinect-wall-harp-lead |
scope owner and wave captain | this skill | _workspace/kinect-wall-harp/00_plan.md |
kinect-wall-harp-prototyper |
live FreenectTD/Kinect wall prototype and calibration findings | tdmcp bridge/tools | _workspace/kinect-wall-harp/01_prototype.md |
kinect-wall-harp-tool-builder |
new Layer 1 tool file + focused unit test | td-feature-build |
_workspace/kinect-wall-harp/02_build_tool.md |
kinect-wall-harp-integrator |
single-writer registry, CLI, recipe, docs | td-feature-integrate |
_workspace/kinect-wall-harp/03_integrate.md |
kinect-wall-harp-qa |
offline gates, boundary QA, live TD/Kinect validation | td-feature-qa |
_workspace/kinect-wall-harp/04_qa.md |
Use existing tdmcp-bridge-engineer only if implementation proves that a new
bridge REST endpoint is necessary. The default plan should avoid a new endpoint
and use the existing bridge execution path.
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.
- 12d ago First seen · 204 lines · 97 tokens per session scan A aaaf1ea4f0ef
tdmcp-kinect-wall-harp is a skill published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 27d ago), licensed MIT. It adds 97 tokens to every session and 1,988 once invoked, about $0.0005 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 skills, from other repositories
broadcast-technical-director
Use when a task needs the judgment of a Media Technical Director/Manager — calling a live broadcast switcher and owning the technical readiness sign-off, designing router/path redundancy and PTP failover for an IP production, resolving a timecode or loudness compliance defect found in rehearsal, or running the…
broadcast-technician
Use when a task needs the judgment of a Broadcast Technician — diagnosing a transmitter power/VSWR alarm, triaging an EAS (Emergency Alert System) relay failure, chasing a loudness-compliance complaint back to its source, or building the redundancy/failover plan for a master-control or transmitter site.
popx-touchdesigner
Local POPX knowledge base and workflow for TouchDesigner. Use when the user mentions POPX, popsextension, POPX examples, POPX operators, or wants to build, inspect, explain, debug, or modify POPX-based setups in TouchDesigner using the bundled POPX reference corpus and live example loader when available.
tdpilot-core
Core patching discipline for TDPilot v2.4.1 — the AI assistant inside TouchDesigner. Use for all work through the td MCP tools: routing intent, inspecting live state, making safe edits, validating results, and recalling or learning local techniques.
tdpilot-production
Production-grade TouchDesigner MCP workflow for TDPilot v2.4.1 (114 tools): show-safe routing, bounded inspection, staged transactions, rollback, performance checks, preservation assertions, and evidence-based handoff.
spark-training-gotchas
Preflight and diagnose the ten known failure modes for ML training on NVIDIA DGX Spark. Use when a training run on DGX Spark fails to start, OOMs below the 128GB limit, slows down mid-run, or before any multi-hour training job on GB10.