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 OthmanAdi/loophole --skill ableton-livegit clone --depth 1 https://github.com/OthmanAdi/loopholeWrote 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/othmanadi/loophole/ableton-live)<a href="https://agentmods.dev/skills/othmanadi/loophole/ableton-live"><img src="https://agentmods.dev/badge/skills/othmanadi/loophole/ableton-live/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/othmanadi/loophole/ableton-live"><img src="https://agentmods.dev/badge/skills/othmanadi/loophole/ableton-live.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00090 | $0.01250 |
| Opus 5 | $0.00045 | $0.00625 |
| Sonnet 5 | $0.00018 | $0.00250 |
| Haiku 4.5 | $0.00009 | $0.00125 |
Grade A, and why
ableton-live 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ableton-live (alias: loophole)
A thin developer-experience layer for the Loophole Bridge, the MCP server that controls Ableton Live 12 over the official Extensions SDK. This skill closes the loop between "the bridge is installed" and "the agent uses it well." It does three things and nothing more.
It never talks to Live directly. It does not embed tool logic, re-implement the bridge, or import any bridge or SDK code. The bridge is the only thing that touches the Live Object Model. Every Live operation in this skill is a call to one of the bridge's MCP tools.
What this skill does
/doctorruns five prerequisite checks (Live running, extension installed, Node version, bridge port reachable, token present) and prints a PASS or a specific FIX line for each, then one verdict. Seedoctor.md. It never auto-runs/setup./setupreads the port and bearer token frombridge.json, then emits one merge-safe MCP client block for Claude Code, Claude Desktop, or Cursor. It never writes or replaces a config file. Seesetup.md.- Recipes are reusable snippets for common Live edits, each a named sequence of real bridge tool calls. See
recipes/:humanize-midi,build-arrangement,batch-rename,chord-from-prompt.
How the pieces connect
flowchart LR
U["User intent"] --> SK["ableton-live skill"]
SK --> DOC["/doctor: 5 checks"]
SK --> SET["/setup: emit merge-safe config block"]
SK --> REC["recipes: tool sequences"]
DOC -. "reads" .-> BJ["bridge.json"]
SET -. "reads" .-> BJ
REC --> BR["Loophole Bridge (MCP tools)"]
BR --> LIVE["Ableton Live 12 Suite"]
classDef accent fill:#E9A23B,stroke:#9A6A1A,color:#160F02,font-weight:bold;
class BR accent
The skill reads bridge.json (for /doctor and /setup) and issues MCP tool calls (for recipes). It does not reach past the bridge.
The bridge tools the recipes use
The recipes reference only these registered MCP tools. No recipe invents a tool.
| Tool | Read or write | What it does |
|---|---|---|
live_get_song_overview |
read | tempo, scale, grid, counts, and current opaque track references |
live_find_track |
read | resolve a track name or substring to current opaque track references |
live_list_clips |
read | list a track's session slots and clips with current opaque references |
live_get_notes |
read | read all MIDI notes from one clip |
live_set_tempo |
write | set the Set tempo in BPM |
live_set_track_props |
write | set a track's name, mute, solo, or arm in one serialized mutation |
live_set_notes |
write | replace all MIDI notes in one clip in one serialized mutation |
live_create_track |
write | create one empty MIDI or audio track |
live_create_midi_clip |
write | create an empty MIDI clip in a session clip slot |
live_set_param |
write | set one device parameter using its returned opaque session reference |
live_insert_device |
write | insert a built-in Live device on a track |
live_render_track |
write | render a track's pre-FX audio over a beat range to a WAV |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 73 lines · 90 tokens per session scan A 1ddfe735436b
ableton-live is a skill published in the GitHub repository OthmanAdi/loophole (16 stars, last pushed 2d ago), licensed MIT. It adds 90 tokens to every session and 1,250 once invoked, about $0.0005 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-extension
Build, modify, and debug Ableton Live extensions written with the @ableton-extensions/sdk — TypeScript/Node.js code that runs in Live's Extension Host. Use this whenever the user is working on an Ableton Live extension: scaffolding a new one, adding context-menu actions or commands, navigating or mutating the Live Set…
groove-builder
Use when the user wants drum patterns by genre - kick, snare, hi-hat, percussion. Examples - "give me a trap beat", "house drum pattern", "DnB drums at 174", "lo-fi drums with swing", "boom-bap pattern".
midi-cleanup
Use when the user asks to humanize a MIDI part, fix voice leading, quantize notes, clean up timing, fix stuck/duplicate notes, or generally polish a MIDI clip they recorded or wrote. Examples - "humanize this hat", "voice these chords better", "the timing is too stiff", "fix the voice leading on the strings".
mixer-doctor
Use when the user describes a mix problem ("muddy", "harsh", "no headroom", "vocals get lost", "kick and bass fighting") or asks for a mix audit. Diagnoses the issue from session state and proposes specific corrective moves with EQ, compression, sends, and routing.
producer-mode
Use when the user asks to set up tracks, pick instruments, scaffold an arrangement, build a project template, or describe a track they want to make in Ableton Live. Examples - "make me a 4-bar lo-fi loop", "set up a film score template", "I want to start a hip-hop beat in C minor".
reference-match
Use when the user references another track they want to emulate the vibe/sound of. Examples - "make this sound like Ólafur Arnalds", "I want a Tame Impala vibe", "match the mix of Kendrick's Money Trees". Translates artist/track references into actionable production decisions.