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 agentmods add skills/pantani/ableton-mind/runtime-release-auditnpx skills add Pantani/ableton-mind --skill runtime-release-auditgit 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/runtime-release-audit)<a href="https://agentmods.dev/skills/pantani/ableton-mind/runtime-release-audit"><img src="https://agentmods.dev/badge/skills/pantani/ableton-mind/runtime-release-audit.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 | $0.00052 | $0.00269 |
| Opus 5 | $0.00026 | $0.00134 |
| Sonnet 5 | $0.00010 | $0.00054 |
| Haiku 4.5 | $0.00005 | $0.00027 |
Grade A, and why
runtime-release-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 4d 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
Runtime Release Audit
Use this skill to prove that the current checkout can build, package and run without performing irreversible publish actions.
Workflow
- Verify version sync across package.json, package-lock.json, dxt/manifest.json, server.json and safeskill.manifest.json.
- Build and inspect dist and bin entrypoints.
- Run DXT/MCPB check mode and inspect generated bundle contents when needed.
- Run npm pack dry-run and compare included files with package expectations.
- Build docs and Docker image when required by the audit scope.
- Smoke CLI bins after build.
- Run mock bridge tests. Run real Live or Push smoke only when the user confirms the environment is ready.
- Do not run npm publish, gh release create/upload, Docker push or registry submit without explicit confirmation.
Report Format
Write _workspace/quality-audit/runtime-release-{N}.md with:
- Artifact.
- Command.
- Result.
- Evidence.
- Release risk.
- Blocked checks with prerequisites.
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.
- 4d ago First seen · 30 lines · 52 tokens per session scan A 041e8e1a75f8
runtime-release-audit is a skill published in the GitHub repository Pantani/ableton-mind (5 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 269 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
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".
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"…
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".
arrangement-coach
Use when the user has a Session-view loop and wants to promote it to a full Arrangement, build sections (intro/verse/drop/break/outro), or extend a 4-bar idea into a 3-minute track. Examples - "turn this loop into a full song", "build me a 2-minute arrangement from this", "promote session to arrangement".