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 groove-buildergit 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/groove-builder)<a href="https://agentmods.dev/skills/glincker/ableton-skills/groove-builder"><img src="https://agentmods.dev/badge/skills/glincker/ableton-skills/groove-builder/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/glincker/ableton-skills/groove-builder"><img src="https://agentmods.dev/badge/skills/glincker/ableton-skills/groove-builder.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.00060 | $0.01272 |
| Opus 5 | $0.00030 | $0.00636 |
| Sonnet 5 | $0.00012 | $0.00254 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
groove-builder 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Groove Builder
Generate idiomatic drum patterns by genre with proper humanization. Writes to MIDI clips on the user's drum track.
Workflow
1. Identify genre + tempo
Required: genre. Optional: tempo (use genre defaults).
| Genre | Default tempo | Time sig |
|---|---|---|
| Lo-fi hip-hop | 70-90 | 4/4 |
| Boom-bap | 85-95 | 4/4 |
| Trap | 130-150 (half-time feel) | 4/4 |
| House | 120-128 | 4/4 |
| Tech house | 124-128 | 4/4 |
| Techno | 125-135 | 4/4 |
| DnB / Jungle | 165-180 | 4/4 |
| UK garage | 130-138 | 4/4 (shuffled) |
| Drill (UK) | 140-145 (half-time) | 4/4 |
| Reggaeton | 95-100 | 4/4 (dembow) |
2. Verify drum rack
get_track_info on the drum track. Confirm a drum rack is loaded with at least kick (C1), snare (D1), hat (F#1), and optionally clap (D#1), open hat (A#1), perc (G1+).
If no kit loaded → ask user, or load stock Ableton Drum Kit.
3. Write the pattern
For a 1-bar (16-step) pattern, here are tested templates:
Lo-fi hip-hop
Kick: X . . . . . X . . . . . . . . .
Snare: . . . . X . . . . . . . X . . . (snare on 5 & 13 for half-time feel)
Hat: X . X . X . X . X . X . X . X . (8th notes)
- Kick: vel 100-110
- Snare: vel 90-100, slight late timing (+5ms)
- Hat: vel 65-85, ±15 humanize, swing 8-12%
Boom-bap
Kick: X . . X . . X . . . X . . . . .
Snare: . . . . X . . . . . . . X . . .
Hat: X X X X X X X X X X X X X X X X (16ths)
- Hat: vel 50-80, more aggressive humanize ±20
Trap
Kick: X . . . . . . X . . . . . . . . (sparse, half-time feel)
Snare: . . . . X . . . . . . . X . . .
Hat: X X . X X X . X X . X X X . X X (rolling, with stutters)
808: long held bass notes underneath
- Hi-hat rolls: alternate 16ths with 32nd-note bursts
- Open hat occasionally on the off-beat
House
Kick: X . . . X . . . X . . . X . . . (4-on-the-floor)
Clap: . . . . X . . . . . . . X . . .
Hat: . . X . . . X . . . X . . . X . (off-beat 8ths)
OpHat: . X . . . X . . . X . . . X . . (between beats)
- Kick: vel 110, locked on grid
- Clap: vel 95
- Hat: tight, minimal humanize
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 · 113 lines · 60 tokens per session scan A 1e63db88020a
groove-builder is a skill published in the GitHub repository glincker/ableton-skills (24 stars, last pushed 17d ago), licensed MIT. It adds 60 tokens to every session and 1,272 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-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.
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.