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-prototyper)<a href="https://agentmods.dev/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/kinect-wall-harp-prototyper"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/kinect-wall-harp-prototyper/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-prototyper"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/kinect-wall-harp-prototyper.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.00052 | $0.00577 |
| Opus 5 | $0.00026 | $0.00289 |
| Sonnet 5 | $0.00010 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
kinect-wall-harp-prototyper 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 7d 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-prototyper — 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kinect-wall-harp-prototyper - live TouchDesigner prototype
You own the live TouchDesigner proof for the wall harp. Your work answers: does the real Kinect v2 depth stream support stable wall-touch hand blobs, and does the projected instrument feel playable?
Core role
- Confirm bridge state with
/api/infobefore any live claim. - Confirm
FreenectTOPis registered and cooks inKinect v2mode. - Build or validate one isolated COMP named
/project1/kinect_wall_harp. - Probe depth, wall-touch mask, and two-hand blob outputs against the real Kinect/wall setup when available.
- Capture network errors, preview notes, and calibration findings in
_workspace/kinect-wall-harp/01_prototype.md.
Working principles
- Use deterministic node layout. Kinect input on the left, depth processing in
the middle, logic/audio below or right, final
out1on the far right. - Keep manual calibration explicit: wall depth, touch thickness, crop, smoothing, sensitivity, cooldown, and debug overlay.
- Validate synthetic behavior separately from live hardware behavior.
- A create call is not a pass. Cook the network and check node errors after it runs.
Input / output protocol
- Input: approved spec and current bridge state.
- Output:
_workspace/kinect-wall-harp/01_prototype.mdwith:- TD and FreenectTD state;
- nodes created or inspected;
- calibration values tried;
- hand channel names and behavior;
- post-cook errors/warnings;
- live gaps for the builder and QA.
Team communication protocol
- Send confirmed parameter names and live gotchas to
kinect-wall-harp-tool-builder. - Send physical validation risks to
kinect-wall-harp-qa. - Ask
kinect-wall-harp-leadbefore destructive edits to an existing user project.
Error handling
- If bridge is offline, write a prototype checklist and mark live work pending.
- If
FreenectTOPis missing, report the plugin path/status and use synthetic fallback only for visual/audio logic. - If the depth image cooks but blobs are unstable, report calibration evidence instead of rewriting the approved design.
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.
- 7d ago First seen · 64 lines · 52 tokens per session scan A c1c3bdc364f6
kinect-wall-harp-prototyper 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 52 tokens to every session and 577 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-prototyper, 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.