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 commands/glincker/ableton-skills/ableton-exportgit 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/commands/glincker/ableton-skills/ableton-export)<a href="https://agentmods.dev/commands/glincker/ableton-skills/ableton-export"><img src="https://agentmods.dev/badge/commands/glincker/ableton-skills/ableton-export.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.00033 | $0.00353 |
| Opus 5 | $0.00016 | $0.00177 |
| Sonnet 5 | $0.00007 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
ableton-export 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 5d 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
/ableton-export
Run a pre-export audit and surface anything that would compromise the bounced file.
What it checks
| Check | Pass criteria |
|---|---|
| Master peak | Below -1 dB |
| Master headroom | At least -3 dB before limiter |
| Track-level clipping | No track meter in red |
| Mono compatibility | All elements audible in mono fold |
| DC offset on master | None |
| Sub-30Hz content | Filtered or controlled |
| Project sample rate | Matches export setting (44.1 / 48 / 96 kHz) |
| Bit depth | 24-bit for archival, 16-bit only for distribution |
| Render mode | Real-time off (unless using external hardware) |
| Normalize | OFF |
| Convert to mono | OFF (unless explicitly mono export) |
| Inactive devices | Bypass or remove for performance |
Workflow
- Read master bus state, track meters, devices.
- Run each check, mark ✅ or ❌.
- Print a summary table.
- If ❌, propose fixes with specific values.
- If all ✅, give the green light: "Ready to export. Recommended settings: 24-bit, 48 kHz, render off, no normalize."
Don'ts
- Don't export on the user's behalf — they may want to choose the file location and name.
- Don't apply mastering chain. This is a check, not a process.
- Don't recommend a specific filename pattern unless asked.
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.
- 5d ago First seen · 40 lines · 33 tokens per session scan A b6c2488e39cf
ableton-export is a command published in the GitHub repository glincker/ableton-skills (22 stars, last pushed 12d ago), licensed MIT. It adds 33 tokens to every session and 353 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-30.
Other commands, from other repositories
beat
Guided beat creation — create a beat from scratch with genre, tempo, and instrumentation choices.
mix
Mixing assistant — analyze and balance track levels, panning, and sends.
sounddesign
Sound design workflow — load instruments and effects, shape parameters for a target sound.
arrange
Guided arrangement — build song structure with sections, transitions, and energy flow.
evaluate
Evaluate recent changes — run the full before/after evaluation loop and recommend keep or undo.
perform
Performance mode — enter a safety-constrained live performance context with energy tracking and safe moves.