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/test-coverage-expansion/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/test-coverage-expansion)<a href="https://agentmods.dev/skills/pantani/ableton-mind/test-coverage-expansion"><img src="https://agentmods.dev/badge/skills/pantani/ableton-mind/test-coverage-expansion.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.00054 | $0.00281 |
| Opus 5 | $0.00027 | $0.00140 |
| Sonnet 5 | $0.00011 | $0.00056 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
test-coverage-expansion 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.
What it actually says
Test Coverage Expansion
Use this skill when audit findings need tests or when code lacks nearby coverage.
Workflow
- Map changed or risky implementation files to existing tests.
- Identify coverage gaps that protect public behavior, not trivia.
- Add focused failing tests before fixes when feasible.
- Keep default tests offline and deterministic. Use fakes for Ableton Live and Push behavior.
- Prefer existing Vitest and Python unittest patterns.
- Run focused tests first, then broader suite when the change surface justifies it.
Coverage Priorities
- MCP tool schemas, validation errors and verify/diff behavior.
- JSON-RPC bridge handler shapes and error handling.
- CLI doctor and install failure modes.
- Distribution package contents and manifest/version sync.
- Recipe and knowledge consistency.
- Regression tests for every BLOCKER or MAJOR audit fix.
Report Format
Write _workspace/quality-audit/test-coverage-{N}.md with:
- Gap.
- Existing tests checked.
- Test added or proposed.
- Command run.
- Remaining risk.
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 · 36 lines · 54 tokens per session scan A e211d8eab540
test-coverage-expansion is a skill published in the GitHub repository Pantani/ableton-mind (5 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 281 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-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.