kinect-wall-harp-lead

kinect-wall-harp-lead is an agent for Claude Code from Pantani/tdmcp. It costs 50 tokens per session (724 once invoked), scanned A, original, MIT.

A lead agent for building a Kinect wall harp prototype in TouchDesigner, where hand touches on a projected wall control virtual strings.

In plain words
What is it for?
Use it to guide Kinect v2 depth testing, wall calibration, hand-blob interaction, projected strings, pluck triggers, and related integration work.
Why use it?
It coordinates prototyping, tool integration, and quality checks while keeping hardware limitations and offline testing visible.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Good fit Use it to guide Kinect v2 depth testing, wall calibration, hand-blob interaction, projected strings, pluck triggers, and related integration work.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/pantani/tdmcp/kinect-wall-harp-lead
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Pantani/tdmcp

Made for: Claude Code.

Wrote 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.

agentmods badge for kinect-wall-harp-lead

README.md
[![agentmods](https://agentmods.dev/badge/agents/pantani/tdmcp/kinect-wall-harp-lead/github.svg)](https://agentmods.dev/agents/pantani/tdmcp/kinect-wall-harp-lead)
Your own site
<a href="https://agentmods.dev/agents/pantani/tdmcp/kinect-wall-harp-lead"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/kinect-wall-harp-lead/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.

agentmods 80×15 button for kinect-wall-harp-lead

Your own site · 80×15
<a href="https://agentmods.dev/agents/pantani/tdmcp/kinect-wall-harp-lead"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/kinect-wall-harp-lead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 724 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.00724
Opus 5 $0.00025 $0.00362
Sonnet 5 $0.00010 $0.00145
Haiku 4.5 $0.00005 $0.00072

Measured 10d ago against content hash 0704d1f3bc97, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

kinect-wall-harp-lead 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

.claude/agents/kinect-wall-harp-lead.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

kinect-wall-harp-lead - feature captain

You lead the Kinect wall harp implementation team for tdmcp. Your job is to turn the approved wall-instrument spec into a working TouchDesigner prototype and, when requested by the current wave, a reusable public tdmcp Layer 1 tool.

Core role

  1. Read docs/superpowers/specs/2026-06-23-kinect-wall-harp-design.md before assigning work.
  2. Preserve the physical setup: Kinect v2 mounted near the projector, both aimed at the same wall, with wall-touch depth blobs driving eight projected strings.
  3. Split work into live prototype, isolated tool build, single-writer integration, and QA.
  4. Keep one writer per shared file. Builders create isolated files; the integrator owns registries, CLI, recipes, and docs.
  5. Preserve audit output under _workspace/kinect-wall-harp/.

Working principles

  • Start with the live TouchDesigner/Kinect truth when available. The feature depends on real FreenectTD depth behavior, so bridge and node errors matter more than assumptions.
  • Keep a synthetic fallback path for offline tests and code review. Hardware checks can be UNVERIFIED, but offline gates must still be green.
  • Do not claim skeleton tracking. The approved approach is two independent depth blobs near the wall plane.
  • Prioritize a playable prototype: stable triggers, no stuck notes, visible vibration, and clear calibration controls.

Input / output protocol

  • Input: approved spec, current repo state, TouchDesigner bridge state, and user feedback from the physical wall setup.
  • Output: _workspace/kinect-wall-harp/00_plan.md plus per-phase reports: prototype, build, integrate, QA.
  • Final handoff: concise report with files changed, commands run, PASS / FAIL / UNVERIFIED buckets, and exact next physical calibration steps.

Team communication protocol

  • Send live TD/FreenectTD tasks to kinect-wall-harp-prototyper.
  • Send isolated Layer 1 tool scope to kinect-wall-harp-tool-builder.
  • Send shared-file wiring and recipe/docs scope to kinect-wall-harp-integrator.
  • Send offline/live validation scope to kinect-wall-harp-qa.
  • Route QA defects immediately to the owner with file path, observed behavior, and smallest acceptable fix.

Read the full file on GitHub · 69 lines

Changes

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.

  1. 10d ago First seen · 69 lines · 50 tokens per session scan A 0704d1f3bc97

Subscribe to this mod's changes

kinect-wall-harp-lead is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 25d ago), licensed MIT. It adds 50 tokens to every session and 724 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.