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/performance-reliability)<a href="https://agentmods.dev/rules/jterratsdev/ableton-live-mcp/performance-reliability"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/performance-reliability/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/performance-reliability"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/performance-reliability.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.00371 | $0.00371 |
| Opus 5.5 | $0.00148 | $0.00148 |
| Sonnet 5.5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
performance-reliability 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
Performance & Reliability
Performance and reliability must be designed, measured, and protected. Do not optimize blindly or defer obvious scalability risks.
Budgets
- Define expected latency, throughput, payload size, memory, storage, and concurrency for high-impact flows.
- User-facing flows should consider p95 and p99 latency, not only averages.
- Establish performance budgets for page weight, render time, API latency, and query count when applicable.
- If no budget exists, propose one before making risky design choices.
Hot Paths
- Avoid N+1 queries, unbounded loops with I/O, repeated serialization, and large synchronous work on request paths.
- Paginate or stream large datasets. Do not load unbounded result sets into memory.
- Load the
collection-standardsskill when implementation, QA automation, or DevOps scripting processes repeated collections, joins lists, scans logs, builds command matrices, or must prove O(n) or bounded complexity. - Keep expensive work outside user-facing request paths through queues, jobs, or precomputation.
- Measure before and after performance changes and report the evidence.
Caching
- Cache only with clear ownership, TTL, invalidation strategy, and stale-data behavior.
- Do not cache sensitive data unless storage, access, and expiration controls are explicit.
- Prefer simple, observable cache strategies before multi-layer cache complexity.
- Document cache keys and invalidation triggers for shared caches.
Reliability
- Design for graceful degradation when dependencies fail.
- Add timeouts, retries, backoff, and circuit breakers for networked dependencies.
- Use bulkheads or queues to protect critical paths from non-critical workload spikes.
- Reliability-sensitive changes need load, stress, or synthetic tests when practical.
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 · 34 lines · 371 tokens per session scan A 3d54c6efa757
performance-reliability is a cursor rule published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 371 tokens to every session, about $0.0015 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.