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.
git 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-snapshot)<a href="https://agentmods.dev/commands/glincker/ableton-skills/ableton-snapshot"><img src="https://agentmods.dev/badge/commands/glincker/ableton-skills/ableton-snapshot/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/commands/glincker/ableton-skills/ableton-snapshot"><img src="https://agentmods.dev/badge/commands/glincker/ableton-skills/ableton-snapshot.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.00044 | $0.00507 |
| Opus 5 | $0.00022 | $0.00253 |
| Sonnet 5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
ableton-snapshot 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.
What it actually says
/ableton-snapshot
Read the full session state and write it to a markdown file as a human-readable snapshot. Useful as:
- A checkpoint before applying risky changes
- A handover document for collaborators
- Personal versioning ("snapshot before the bridge rewrite")
What it captures
- Project metadata: name, tempo, time signature, total length
- Tracks: name, type (MIDI/Audio/Return/Master), color, volume, panning, mute/solo state
- Devices: per-track device chain with key parameter values
- Clips: per-track clip names, lengths, note count for MIDI
- Master chain: full device list with parameters
- Sends/returns: routing matrix
Output format
Default location: ./snapshots/<timestamp>-<sessionname>.md
Example output:
# Snapshot: my-track v3
**Date:** 2026-04-25 14:32
**Tempo:** 95 BPM
**Time sig:** 4/4
## Tracks (8)
### 1. Drums (MIDI, orange)
- Volume: -2.5 dB
- Pan: 0
- Devices: Drum Rack > Compressor (3:1, 4 dB GR) > EQ Eight (HPF 30Hz)
- Clips: lo-fi-kit-loop (4 bars, 64 notes)
### 2. Bass (MIDI, yellow)
- ...
## Master chain
- Glue Compressor (2:1, slow, 1.5 dB GR, bypass)
- Limiter (-1 dB ceiling, bypass)
Workflow
- Read all session data.
- Format as markdown.
- Write to
snapshots/directory in the project root. - Confirm: "Snapshot saved to ./snapshots/2026-04-25-1432-mytrack.md"
Don'ts
- Don't dump every parameter — focus on what matters (volume, key device settings, not every micro-knob).
- Don't include large clip note arrays — note count is enough.
- Don't overwrite existing snapshots — always timestamp.
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 · 62 lines · 44 tokens per session scan A f33467583c4e
ableton-snapshot is a command published in the GitHub repository glincker/ableton-skills (23 stars, last pushed 15d ago), licensed MIT. It adds 44 tokens to every session and 507 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.
arrange
Guided arrangement — build song structure with sections, transitions, and energy flow.
sounddesign
Sound design workflow — load instruments and effects, shape parameters for a target sound.
perform
Performance mode — enter a safety-constrained live performance context with energy tracking and safe moves.
memory
Browse, search, and manage your saved technique library.