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-probe-design/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-probe-design)<a href="https://agentmods.dev/skills/zarfld/presonus-studiolive-mcp/hil-probe-design"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/hil-probe-design/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-probe-design"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/hil-probe-design.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.00000 | $0.01063 |
| Opus 5.5 | $0.00000 | $0.00425 |
| Sonnet 5.5 | $0.00000 | $0.00213 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
hil-probe-design 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 1mo 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HIL Probe Design
Purpose
Use this skill whenever mixer behavior cannot be proven from source code, unit tests, or existing captured real-device fixtures.
HIL means hardware-in-loop. This repository controls or inspects a real PreSonus StudioLive mixer. Routing, AVB patching, Fat Channel scaling, fader taper, aux behavior, and writes must be validated against actual hardware before being claimed as supported.
Applies to
- StudioLive 32SC
- StudioLive 32R / 24R / 16R
- StudioLive III consoles and rack mixers
- AVB/stagebox routing
- local input routing
- output patch routing
- Fat Channel parameters
- fader/mute/aux write behavior
- adapter protocol reverse engineering
Required probe document template
Create or update a probe document using this structure:
# HIL Probe: <probe-name>
## Target behavior
What behavior is being measured?
## Capability impact
Which tools/features can change state if the probe passes?
## Required hardware
- Mixer model:
- Firmware version:
- Stagebox/rack mixer:
- Network path:
- Computer OS:
- Node/pnpm version:
## Safety classification
- Read-only / write
- Live-safe: yes/no
- Required backup/scene save:
## Preconditions
Exact mixer state required before starting.
## Procedure
1. Step-by-step instructions.
2. Each step changes only one variable.
3. Record expected UI/audio/API observations.
## Data to capture
- raw adapter JSON:
- MCP tool response:
- mixer UI screenshot if useful:
- UC Surface screenshot if useful:
- audio observation if useful:
## Pass criteria
Measurable pass conditions.
## Fail criteria
Measurable fail conditions.
## Result recording format
Where to store logs, dumps, fixtures, and summary.
## Capability matrix update
Exact state transition allowed by a passing result.
Required probe output artifacts
A completed probe must produce at least:
docs/hil/<date>-<probe-name>/README.md
docs/hil/<date>-<probe-name>/raw-adapter-state.json
docs/hil/<date>-<probe-name>/mcp-tool-output.json
docs/hil/<date>-<probe-name>/result.md
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.
- 1mo ago First seen · 170 lines · 0 tokens per session scan A ba2a7d37de67
hil-probe-design is a skill published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,063 tokens. 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
apollo-onboarding
Plans and configures a Universal Audio Apollo rig end to end through the uad-console-mcp MCP server, covering the interview questions to ask, which physical input suits which source, the clock master decision for ADAT expanders and other digital gear, ADAT sample-rate and channel-count limits, multi-Apollo Thunderbolt…
apollo-studio-tasks
Runs day-to-day Universal Audio Apollo studio operations through the uad-console-mcp MCP server, including setting up a channel for vocal or instrument tracking with a Unison preamp and correct gain staging, building cue and headphone mixes for one or several performers, wiring up podcast and streaming setups with…
test-bench-export
Export a Kshana scenario's vehicle motion and events (motion CSV, NMEA, waypoints, events) for replay through a laboratory GNSS simulator, then score the receiver under test. Use when a receiver maker or tester wants a scenario's motion and event times for a simulator.
boardrepo
Read and review real PCB projects on BoardRepo. Search published hardware designs, open a board's schematic connectivity, bill of materials and files, run KiCad's DRC and ERC, and check a design against a fabrication house's limits. Use whenever the user names a BoardRepo board or URL, asks to find a published board…
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.
holohub-app-lifecycle
Use for non-failing HoloHub app work with ./holohub: scaffold, build, run, test, visual evidence, lint, and flow benchmarking.