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/hybridlabor-api/bdb-dev-optimized-agent-skillsWrote 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/hybridlabor-api/bdb-dev-optimized-agent-skills/kinect-wall-harp-lead)<a href="https://agentmods.dev/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/kinect-wall-harp-lead"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/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.
<a href="https://agentmods.dev/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/kinect-wall-harp-lead"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/kinect-wall-harp-lead.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.00050 | $0.00724 |
| Opus 5 | $0.00025 | $0.00362 |
| Sonnet 5 | $0.00010 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00072 |
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 6d 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.
This is a copy
100% identical to kinect-wall-harp-lead — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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
- Read
docs/superpowers/specs/2026-06-23-kinect-wall-harp-design.mdbefore assigning work. - 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.
- Split work into live prototype, isolated tool build, single-writer integration, and QA.
- Keep one writer per shared file. Builders create isolated files; the integrator owns registries, CLI, recipes, and docs.
- 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.mdplus 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.
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.
- 6d ago First seen · 69 lines · 50 tokens per session scan A 0704d1f3bc97
kinect-wall-harp-lead is an agent published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 5d ago), licensed Apache-2.0. 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. It is 100% identical to kinect-wall-harp-lead, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
creative-analyzer
Use this agent after cycle completion or when the user wants creative analysis of features, viral potential, wow moments, and product differentiation. Focuses on WHAT to build next — not interaction quality (that's ux-analyzer). Context: User completed a cycle and wants to know what to build next. user: "What should…
muse
The creative product mind that knows why some features become part of someone's identity and others get used once. Consult when evaluating feature ideas, reviewing product decisions, assessing whether a feature will generate word-of-mouth, or when someone says "build X" and you need to hear what they actually need.…
riff
The riff partner - a thinking companion for creative collaboration moments. Consult when brainstorming, stuck on a design, ideating a feature, debating an approach, wanting a second opinion on a half-formed thought, or when you're tired and need someone in the room rather than another instructor. Trigger conditions…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.