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 lucasmaher-hash/touch-designer-mcp --skill mixer-scene-contractgit clone --depth 1 https://github.com/lucasmaher-hash/touch-designer-mcpWrote 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/lucasmaher-hash/touch-designer-mcp/mixer-scene-contract)<a href="https://agentmods.dev/skills/lucasmaher-hash/touch-designer-mcp/mixer-scene-contract"><img src="https://agentmods.dev/badge/skills/lucasmaher-hash/touch-designer-mcp/mixer-scene-contract/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/lucasmaher-hash/touch-designer-mcp/mixer-scene-contract"><img src="https://agentmods.dev/badge/skills/lucasmaher-hash/touch-designer-mcp/mixer-scene-contract.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.00084 | $0.00384 |
| Opus 5 | $0.00042 | $0.00192 |
| Sonnet 5 | $0.00017 | $0.00077 |
| Haiku 4.5 | $0.00008 | $0.00038 |
Grade A, and why
mixer-scene-contract 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 9d 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 mixer-scene-contract — 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.
What it actually says
mixer-scene-contract
Design the structured contract for approved mixer scene changes. This skill is for design/spec work, not implementation.
Context to read
src/automation/showDirectorSchema.tssrc/automation/showDirectorRuntime.tssrc/cli/agent.tsaroundshow-directortests/unit/showDirector.test.tstests/unit/cliAgent.test.ts
Design rules
- Keep mixer scene changes separate from generic
arm_effect. - The MVP operation is "arm scene/cue for approval", not autonomous execution.
- Require explicit names or IDs:
show_name,snapshot_name,cue_name,scene_id, orsetlist_ref. Do not design fuzzy live lookup as execution. - Preserve blocked/operator-only semantics for
mixer_gain,pa_mute, andaudio_routing. - Every accepted request needs an audit entry with request, intent, decision, approval ID, operator, and adapter target.
Output
Write _workspace/ai-party-mixer/01_contract.md with:
- proposed schema fields and examples;
- approval and audit model;
- CLI dry-run examples;
- mapping to action plans;
- compatibility notes;
- unit-test checklist.
Quality bar
The result should be specific enough that a builder can implement it without asking what fields exist or how approval flows.
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.
- 9d ago First seen · 45 lines · 84 tokens per session scan A 71d0d375a8c4
mixer-scene-contract is a skill published in the GitHub repository lucasmaher-hash/touch-designer-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 84 tokens to every session and 384 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to mixer-scene-contract, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
mavlink-integration
Use this skill when a task involves MAVLink protocol communication via pymavlink, UART/UDP/TCP drone connections, ArduPilot SITL simulation, or telemetry message parsing in the edge service. Don't use it for raw UART hardware driver code without MAVLink framing (use embedded-systems), WebSocket transport to the web…
hdl-module-design
Use when writing, refactoring, or deciding how to test an HDL module, component, or IP block (ROHD, Chisel, SpinalHDL, Verilog, VHDL) and you need it parameterized, validated, and covered by exhaustive tests rather than a one-off.
unity-ceedling-integration
Use when adding, configuring, or debugging Unity, Ceedling, CMock, or embedded C unit tests, mocks, fixtures, build variants, or CI test runs.
embedded-systems
Use this skill when writing or reviewing Python code for Raspberry Pi 5 edge devices -- UART hardware drivers, camera streaming via picamera2, GPIO control, systemd services, or resource monitoring. Don't use it for MAVLink protocol parsing (use mavlink-integration), web portal server code, or Helm work.
embedded-testing-patterns
Embedded C test patterns using Unity, CMock, Ceedling, and QEMU.
external-gitcode-ascend-ascendc-operator-testcase-gen
A test-case design tool for AscendC operators, which are custom computation kernels for Ascend AI hardware. It helps create unit, accuracy, benchmark, and generalized test cases.