Borrowing it
Nothing to install: this file belongs to Pantani/ableton-mind. 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/Pantani/ableton-mind/main/.agents/skills/ableton-mind-build/SKILL.mdgit clone --depth 1 https://github.com/Pantani/ableton-mindWrote 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/pantani/ableton-mind/ableton-mind-build)<a href="https://agentmods.dev/skills/pantani/ableton-mind/ableton-mind-build"><img src="https://agentmods.dev/badge/skills/pantani/ableton-mind/ableton-mind-build/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/pantani/ableton-mind/ableton-mind-build"><img src="https://agentmods.dev/badge/skills/pantani/ableton-mind/ableton-mind-build.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.00036 | $0.00667 |
| Opus 5 | $0.00018 | $0.00333 |
| Sonnet 5 | $0.00007 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
ableton-mind-build 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ableton-mind-build — Team Orchestrator
Use this skill whenever the user asks to execute, implement, continue, scaffold, redo, synchronize, evaluate or gate concrete work for ableton-mind. Conceptual questions about PLAN.md can be answered directly without launching a full cycle.
Team
| Track | Agent | Domain |
|---|---|---|
| Lead | architect | plan, ADRs, integration, phase gates |
| A — Server | ts-server-engineer | TS/Node MCP server, tools, resources, prompts |
| A — Bridge | python-bridge-engineer | Python Remote Script, LiveAPI, TCP JSON-RPC |
| B — Knowledge | knowledge-curator | device schemas, packs, scales, MIDI data |
| C — Recipes | recipe-designer | JSON music recipes |
| D — Distribution | distribution-docs-engineer | MCPB/DXT, npm, Docker, docs, CI, CLI |
| E — QA | qa-integration | parity, contract drift, recipe lint, smoke, gate |
Phase 0 — Always Gather Context First
- Read PLAN.md.
- Read _workspace/PROGRESS.md if it exists.
- List _workspace/decisions/ and _workspace/qa/.
- List _workspace/cycle-briefing-*.md.
- Choose the mode:
| Mode | When | Action |
|---|---|---|
| Initial | PROGRESS.md does not exist | Create workspace state and plan Phase 0 spike |
| Continue | PROGRESS.md points to ongoing work | Write the next cycle briefing and continue |
| Redo phase | User requests a redo | Archive current workspace and recreate the requested scope |
| Phase gate | QA exists but PROGRESS is stale | Read verdict, update PROGRESS and decide next cycle |
| Sync only | User asks status | Report state without dispatching tracks |
Cycle Briefing
The architect writes _workspace/cycle-briefing-{N}.md with: PLAN phase, one-sentence goal, assignments per track, changed contracts, dependencies and gate criteria. Keep tasks concrete and file-scoped.
Execution
Run tracks in parallel only when their write scopes do not conflict and the current tooling/user permission allows sub-agents. Phase 0 spike is sequential: contract, bridge, server, integration. Later phases can run server, bridge, knowledge, recipes, distribution and QA in parallel as dependencies allow.
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 · 58 lines · 36 tokens per session scan A a3e4f4a2b746
ableton-mind-build is a skill published in the GitHub repository Pantani/ableton-mind (5 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 667 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
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"…
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.