Borrowing it
Nothing to install: this file belongs to zarfld/presonus-studiolive-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zarfld/presonus-studiolive-mcp/master/.github/Skills/hil-validation/SKILL.mdgit clone --depth 1 https://github.com/zarfld/presonus-studiolive-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/zarfld/presonus-studiolive-mcp/hil-validation)<a href="https://agentmods.dev/skills/zarfld/presonus-studiolive-mcp/hil-validation"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/hil-validation/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/zarfld/presonus-studiolive-mcp/hil-validation"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/hil-validation.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.00024 | $0.01062 |
| Opus 5 | $0.00012 | $0.00531 |
| Sonnet 5 | $0.00005 | $0.00212 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
hil-validation 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hardware-in-the-loop validation
Use this skill when
Use this skill when:
- making claims about real StudioLive hardware
- validating firmware-specific behavior
- promoting
implemented-unverified,inferred, orprobe-requiredcapability toverified - adding or changing
*.hil.test.ts - changing probe CLI behavior
- validating routing, Fat Channel parameter mapping, meters, discovery, scenes, or write tools
- updating hardware support tables
Goal
Ensure that hardware claims are supported by repeatable evidence. Unit tests and fixtures are useful but do not prove hardware compatibility across mixer models or firmware versions.
Evidence levels
| Level | Meaning | May support README hardware claim? |
|---|---|---|
static-code |
Code inspection only | No |
unit-test |
Pure test without mixer | No, except internal logic |
fixture-replay |
Replay of prior captured mixer state | Partial, if capture metadata exists |
manual-probe |
Operator command/output saved | Yes, limited to tested model/firmware |
automated-hil |
Repeatable HIL test against real mixer | Yes, strongest |
live-show |
Used during real soundcheck/show with notes | Yes, but must still state scope |
Required capture metadata
Every hardware capture or HIL result must record:
mixerModel: "StudioLive 32SC"
firmware: "3.3.0.109659"
serialRedacted: true
connection: "LAN TCP 53000"
serverCommit: "<git-sha>"
nodeVersion: "<node-version>"
pnpmVersion: "<pnpm-version>"
command: "pnpm probe:dev dump-state -d <ip>"
capturedAt: "<ISO-8601>"
operator: "<initials or omitted>"
purpose: "routing probe / Fat Channel probe / discovery / meter validation"
limitations:
- "Single mixer model only"
- "No 32R stagebox connected"
Do not commit private IP addresses, serial numbers, venue names, personal names, or show-specific confidential data unless explicitly intended.
Procedure
- Define the claim to validate.
- Example: “AUX 1 send levels can be extracted for line channels.”
- Example: “Output patch source index is observable but source name is not yet mapped.”
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.
- 10d ago First seen · 117 lines · 24 tokens per session scan A 795511d34bbb
hil-validation is a skill published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 1,062 once invoked, about $0.0001 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-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.