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 skills add jterratsdev/ableton-live-mcp --skill doc-syncgit clone --depth 1 https://github.com/jterratsdev/ableton-live-mcpWrote 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/jterratsdev/ableton-live-mcp/doc-sync)<a href="https://agentmods.dev/skills/jterratsdev/ableton-live-mcp/doc-sync"><img src="https://agentmods.dev/badge/skills/jterratsdev/ableton-live-mcp/doc-sync/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/skills/jterratsdev/ableton-live-mcp/doc-sync"><img src="https://agentmods.dev/badge/skills/jterratsdev/ableton-live-mcp/doc-sync.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.00000 | $0.00561 |
| Opus 5.5 | $0.00000 | $0.00224 |
| Sonnet 5.5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
doc-sync 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 1mo 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Sync
Keep architecture docs, changelog, onboarding, runbooks, site copy, and prompt registers aligned with delivered changes.
When To Load
- Trigger:
documentation - Trigger:
docs - Trigger:
changelog - Trigger:
readme - Trigger:
quickstart - Trigger:
runbook - Trigger:
architecture - Trigger:
adr - Trigger:
release notes - Trigger:
public site - Trigger:
prompt registry
Procedure
- Identify changed behavior, architecture, release surface, workflows, commands, and user-facing copy from the task, issue, diff, and evidence.
- Update the smallest authoritative documentation surfaces for the audience: README for onboarding, CHANGELOG for release history,
docs/for architecture and runbooks,.generated-prompts/for prompt intent, and the public site for product-facing guidance. - Keep code, service, and domain generation prompts traceable: update
.generated-prompts/code.mdor.generated-prompts/services.mdafter substantial class, model, service, controller, or module changes. - Keep documentation and diagram prompts traceable: update
.generated-prompts/docs.mdor.generated-prompts/diagrams.mdafter substantial docs, architecture, ADR, runbook, changelog, or Mermaid changes. - Run
orchestra doc-sync audit --task <id>before handoff when documentation, changelog, architecture, diagram, or public-site surfaces changed. Use--strictin CI or release checks that should fail on missing prompt registry coverage. - If the audit reports repeated documentation iterations, use
orchestra lessons assistto capture the reusable correction pattern after verification. - Validate command examples against
orchestra commands manifest --json,orchestra --help, or the repo-localnode bin/orchestra.jsduring Open Orchestra development. - If README, docs, or site onboarding changes, check the sibling surfaces so quickstart language, command names, and release positioning do not drift.
- Record unresolved documentation gaps as review findings or follow-up tasks instead of burying them in prose.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 43 lines · 0 tokens per session scan A 002138d8ac03
doc-sync is a skill published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 561 tokens. 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…