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/sound-engineer-boundary-yagni/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/sound-engineer-boundary-yagni)<a href="https://agentmods.dev/skills/zarfld/presonus-studiolive-mcp/sound-engineer-boundary-yagni"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/sound-engineer-boundary-yagni/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/sound-engineer-boundary-yagni"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/sound-engineer-boundary-yagni.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.00038 | $0.01082 |
| Opus 5 | $0.00019 | $0.00541 |
| Sonnet 5 | $0.00008 | $0.00216 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
sound-engineer-boundary-yagni 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 12d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sound-engineer boundary and YAGNI guardrail
Use this skill when
Use this skill when:
- deciding whether a feature belongs in the MCP server or a sound-engineer agent
- reviewing YAGNI-driven removals or simplifications
- implementing rider, input-list, patch-sheet, soundcheck, monitor, or routing features
- deciding whether a feature should be current scope, later scope, probe-blocked, or external-agent responsibility
- writing README claims about “what the MCP server does”
Goal
Keep the MCP backend narrow but operationally useful.
YAGNI means “do not build speculative features.” It does not mean deleting essential facts, diagnostics, or safety contracts needed for the current soundcheck/routing workflow.
Boundary rule
The MCP backend provides facts, safe validations, and gated operations.
The sound-engineer agent performs interpretation, planning, and decisions.
MCP backend responsibilities
The MCP server should expose:
- mixer discovery and identity
- mixer capabilities and limits
- channel state: names, mute, solo, fader, pan, color, meters
- Fat Channel model/state where available
- patch-sheet validation primitives
- input-list validation primitives
- line-check observations and diagnostics
- monitor/AUX send facts and audits
- routing graph facts with confidence metadata
- stagebox/AVB/output routing probe instructions where not directly observable
- proposed change sets, not autonomous writes
- gated write execution only when explicitly enabled and confirmed
Sound-engineer agent responsibilities
The consuming agent should handle:
- reading and interpreting riders
- deciding the show input list
- assigning microphones and DI boxes
- planning stage patching
- choosing monitor/IEM layout
- deciding whether a route or mix is musically acceptable
- proposing EQ/compression/gate changes
- explaining risks to the human operator
- asking the human to confirm physical patching or probe actions
Scope classification
Classify every disputed feature before removing or implementing it:
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.
- 12d ago First seen · 122 lines · 38 tokens per session scan A 00e692bc365f
sound-engineer-boundary-yagni is a skill published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 1,082 once invoked, about $0.0002 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
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
aws-sdk-java-v2-core
Provides AWS SDK for Java 2.x client configuration, credential resolution, HTTP client tuning, timeout, retry, and testing patterns. Use when creating or hardening AWS service clients, wiring Spring Boot beans, debugging auth or region issues, or choosing sync vs async SDK usage.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…