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/.claude/skills/ableton-mind-quality-audit/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-quality-audit)<a href="https://agentmods.dev/skills/pantani/ableton-mind/ableton-mind-quality-audit"><img src="https://agentmods.dev/badge/skills/pantani/ableton-mind/ableton-mind-quality-audit/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-quality-audit"><img src="https://agentmods.dev/badge/skills/pantani/ableton-mind/ableton-mind-quality-audit.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.00088 | $0.01566 |
| Opus 5 | $0.00044 | $0.00783 |
| Sonnet 5 | $0.00018 | $0.00313 |
| Haiku 4.5 | $0.00009 | $0.00157 |
Grade A, and why
ableton-mind-quality-audit 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ableton-mind-quality-audit - Team Orchestrator
Use this skill for broad quality work: complete audits, command matrix validation, security review, usability and flow review, refactor planning, missing-test coverage, release/runtime readiness and follow-up hardening waves.
Use ableton-mind-build for feature phase execution. Use this skill when the goal is to increase repo quality across existing surfaces.
Team
| Track | Agent | Domain |
|---|---|---|
| Lead | quality-audit-lead | scope, triage, severity, fan-in, remediation gate |
| Commands | command-surface-auditor | package scripts, bins, CI commands, docs commands |
| Security | security-supply-chain-auditor | dependencies, scripts, bridge safety, workflows, Docker |
| Usability | usability-flow-auditor | install, doctor, docs, CLI errors, MCP ergonomics |
| Coverage | test-coverage-engineer | missing tests, regression tests, offline fakes |
| Maintainability | refactor-maintainability-engineer | complexity, duplication, boundaries, safe refactors |
| Runtime | runtime-release-auditor | package artifacts, DXT/MCPB, Docker, docs, release gates |
| Gate | qa-integration | cross-boundary verification after fixes |
Phase 0 - Context And Mode
- Read
PLAN.md,_workspace/PROGRESS.md,_workspace/tech-debt.mdif present, latest_workspace/qareports and latest_workspace/quality-auditreports. - Read
package.json,pyproject.toml,ruff.toml, biome/eslint/tsconfig/vitest config,.github/workflowsandDockerfile. - Check git status. Preserve unrelated local changes.
- Choose mode:
| Mode | When | Action |
|---|---|---|
| Full audit | User asks for complete audit or quality sweep | Create new audit briefing and launch all tracks |
| Targeted audit | User names one area | Launch only relevant tracks plus lead and QA gate |
| Fix wave | User asks to fix audit findings | Read latest report/backlog, add tests first where feasible, patch bounded items |
| Re-run | User asks to re-run or verify | Re-run the command matrix and affected checks only |
| Status | User asks what is pending | Summarize latest report/backlog without launching changes |
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 · 137 lines · 88 tokens per session scan A 74dbd4fb5d5c
ableton-mind-quality-audit is a skill published in the GitHub repository Pantani/ableton-mind (5 stars, last pushed 2mo ago), licensed MIT. It adds 88 tokens to every session and 1,566 once invoked, about $0.0004 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.