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/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/rules/jterratsdev/ableton-live-mcp/release-rollback)<a href="https://agentmods.dev/rules/jterratsdev/ableton-live-mcp/release-rollback"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/release-rollback/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/rules/jterratsdev/ableton-live-mcp/release-rollback"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/release-rollback.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.00350 | $0.00350 |
| Opus 5.5 | $0.00140 | $0.00140 |
| Sonnet 5.5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
release-rollback 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.
What it actually says
Release & Rollback
Every release must be deployable, observable, and reversible. A feature is not ready if the team cannot monitor it or recover from it.
For rollout tooling, synthetic monitoring, SLOs, on-call, and operational reporting categories, see devops-tooling.mdc.
Release Readiness
- Confirm Definition of Done, QA evidence, security review, migration status, and unresolved risks before release.
- Identify deployment target, release owner, release window, affected users, and communication needs.
- List feature flags, configuration changes, migrations, background jobs, and third-party dependencies.
- Verify observability exists for the changed behavior: logs, metrics, traces, dashboards, and alerts when applicable.
Rollout Strategy
- Prefer small, reversible releases over large batches.
- Use feature flags, canaries, phased rollout, or dark launch for risky user-facing or infrastructure changes.
- Database changes must be backward compatible when possible and safe across rolling deploys.
- Long-running migrations must have progress monitoring and an interruption plan.
Rollback Plan
- Every release must state how to rollback code, configuration, feature flags, and migrations.
- If rollback is not possible, document the forward-fix plan and get Product Owner risk acceptance before release.
- Do not release when rollback depends on manual guesswork or undocumented production console changes.
Post-Release
- Monitor agreed signals after release: errors, latency, saturation, conversion, usage, and user-facing failures.
- Define who watches the release and for how long.
- Capture incidents, regressions, and follow-up work as backlog items.
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 · 33 lines · 350 tokens per session scan A c43c17872685
release-rollback is a cursor rule published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 350 tokens to every session, about $0.0014 per session on Opus 5.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 cursor rules, from other repositories
changesets
Changeset format and bump rules enforced by CI.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
release-checklist
What to update with each code change or version release.
github-cli-guide
A guide on how to use the Github CLI (gh cli) especially related to creating issues via the CLI.
release-policy
Release, versioning, and signing policy for setmac.