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 glincker/ableton-skills --skill mastering-prepgit clone --depth 1 https://github.com/glincker/ableton-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/skills/glincker/ableton-skills/mastering-prep)<a href="https://agentmods.dev/skills/glincker/ableton-skills/mastering-prep"><img src="https://agentmods.dev/badge/skills/glincker/ableton-skills/mastering-prep.svg" alt="Measured on agentmods" 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.00069 | $0.00952 |
| Opus 5 | $0.00034 | $0.00476 |
| Sonnet 5 | $0.00014 | $0.00190 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
mastering-prep 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastering Prep
Pre-master audit. Confirm the mix is in a clean state for either external mastering or self-mastering. Does NOT apply final mastering — that's a separate workflow with explicit user intent.
Workflow
1. Read the master bus
get_track_infofor masterget_device_parametersfor any plugins on master- Check current peak level, RMS, LUFS if available
2. Run the audit checklist
For each item, mark ✅ pass or ❌ fail with the specific reading:
| Check | Target | What to look for |
|---|---|---|
| Peak level | -3 to -6 dB | Master should have headroom — never above -1 dB |
| No master limiter active for export-to-mastering | Off | Mastering engineer wants raw mix; remove limiter from master |
| No master compressor over 2 dB GR | <2 dB | Heavy mastering compression on a pre-master is destructive |
| LUFS integrated | -16 to -20 LUFS for pre-master | Too loud = no headroom for mastering |
| Mono compatibility | All elements audible in mono | Toggle Utility's mono switch — verify nothing disappears |
| Phase coherence | Above 0.0 (positive) | Use Spectrum or Stereo & Phase — dips below 0 = destructive cancellation |
| Frequency balance | No spikes >6 dB above neighbors | Bass vs mids vs highs evenly spread |
| Sub-bass below 40 Hz | Cut or controlled | Anything below 30 Hz wastes headroom and clouds masters |
| Above 18 kHz | Cut if no musical content | Tames hiss/artifacts; saves headroom |
| DC offset | None | Use Utility's DC filter on the master |
| Track-level clipping | None | Inspect each track's meter — yellow is fine, red is not |
| Inactive devices | Bypass or remove | Unused devices on tracks waste CPU and confuse archiving |
3. Identify and report
Print the audit table with results. Lead with failures, then warnings, then passes.
"Audit results: ❌ Master peaking at -0.8 dB — needs at least 3 dB more headroom ❌ Vocals on track 3 mono-incompatible — disappears 30% in mono fold ⚠️ LUFS integrated -10.2 — too loud for pre-master, drop master fader 4 dB ✅ Phase coherence 0.7 — good ✅ No DC offset ✅ Sub-bass clean below 30 Hz"*
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 · 74 lines · 69 tokens per session scan A 09dca15c458a
mastering-prep is a skill published in the GitHub repository glincker/ableton-skills (22 stars, last pushed 13d ago), licensed MIT. It adds 69 tokens to every session and 952 once invoked, about $0.0003 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-30.
Other skills, from other repositories
ableton-live
Connect and operate the Loophole Bridge (Ableton Live MCP server). Use when the user wants to check Live/bridge prerequisites, wire an MCP client to Loophole, or run a Live editing recipe (humanize, build arrangement, batch rename, chord from prompt). Triggers: "is my Ableton bridge working", "set up loophole"…
livepilot-creative-director
Use when the user makes an open-ended creative production request — "make it feel like X", "sound like X", "develop this", "mutate", "more interesting", "less generic", "take it somewhere", structure decisions without exact specs, or any reference/style ask. Also use when routerequest returns…
livepilot-core
Core discipline for LivePilot — agentic production system for Ableton Live 12. 474 tools across 57 domains. This skill should be used whenever working with Ableton Live through MCP tools. Provides golden rules, tool speed tiers, error handling protocol, and pointers to domain and engine skills.
livepilot-corpus-builder
Build a private knowledge corpus from your own Live projects, rack library, Max devices, and plugin presets. Use when the user says "build my corpus", "scan my projects", "index my racks", "make atlas of my library", "private atlas from my files", or wants Claude to know their personal sound (not just Ableton's…
livepilot-devices
This skill should be used when the user asks to "load a device", "add an effect", "find a plugin", "device chain", "rack", "preset", "sound design setup", "load instrument", "find a synth", or wants to browse, load, and configure devices in Ableton Live.
livepilot-sound-design-engine
This skill should be used when the user asks to "design a sound", "analyze a patch", "fix a static sound", "add modulation", "check my timbre", "improve a synth patch", or wants critic-driven sound design feedback and iterative patch refinement.