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 instructions/ntworm/ableton-mcp-server/agents-mdgit clone --depth 1 https://github.com/ntworm/ableton-mcp-serverWhat 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.01909 | $0.01909 |
| Opus 5 | $0.00955 | $0.00955 |
| Sonnet 5 | $0.00382 | $0.00382 |
| Haiku 4.5 | $0.00191 | $0.00191 |
Grade A, and why
ableton-mcp-server AGENTS.md 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 3d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — ableton-mcp-server
Purpose
ableton-mcp-server v0.6.0 exposes 96 MCP tools for inspecting and safely mutating an Ableton Live Set. Thirteen are local/headless and 83 may require Ableton Live; the current routes are loopback TCP, loopback WebSocket, composed local calls, and local-only tools. A Python FastMCP process coordinates a Live MIDI Remote Script over TCP and an Ableton Extension over WebSocket. The repository is MIT-licensed and targets Windows-hosted Ableton Live; WSL clients must launch the Windows-native executable.
Read order
- This file for repository-wide rules.
- Only the relevant
.agent-context/{architecture,conventions,dependencies,hot-files,risks}.mdfile. - Current source, tests, Git evidence, and canonical docs for task-specific claims.
Canonical project docs are README.md, docs/ARCHITECTURE.md, docs/TOOL_REFERENCE.md, docs/api_capability_matrix.md, and docs/KNOWN_BUGS.md. Files under prompts/ are proposals/handoffs and can be partially superseded; verify them against current code before acting.
Recent change context (read this if working on transport, capability matrix, or resolved envelope)
The v0.5.2 release landed four coordinated changes driven by the comparison with the public 8309/ableton-agent-hub project. Any agent picking up follow-up work should read the planning and handoff documents first to avoid re-litigating settled decisions:
docs/ABLETON_AGENT_HUB_REFACTORING.md— the original direction-setting plan (compare/contrast, scope decisions, items explicitly NOT to copy from the upstream project).docs/superpowers/specs/2026-08-01-r1-resolved-field.md— the canonical shape of theresolvedsub-object returned by mutation tools; deviating from this spec requires a new spec and a coordinated test update.docs/superpowers/specs/2026-08-01-r4-capability-matrix.md— the design behind the newget_bridge_status.tools/capability_counts/capability_sourcefields; the spec contains a known non-blocking drift note aboutlive_required_tools(57, not 59) that should be reconciled.tasks/v0-5-1-refactor-r1r3/HANDOFF.md— the per-wave status and audit findings for v0.5.2. The current line subsequently implements the bounded R2/R6/E1 follow-ups described below.
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.
- 3d ago First seen · 111 lines · 1,909 tokens per session scan A 9164c39d435f
ableton-mcp-server AGENTS.md is an instructions file published in the GitHub repository ntworm/ableton-mcp-server (2 stars, last pushed 9d ago), licensed MIT. It adds 1,909 tokens to every session, about $0.0095 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.