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/solid-architecture)<a href="https://agentmods.dev/rules/jterratsdev/ableton-live-mcp/solid-architecture"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/solid-architecture/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/solid-architecture"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/solid-architecture.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.00410 | $0.00410 |
| Opus 5.5 | $0.00164 | $0.00164 |
| Sonnet 5.5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
solid-architecture 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
SOLID & Clean Architecture
Single Responsibility (SRP)
- One module = one reason to change. If a file mixes UI rendering with business logic, data access with orchestration, or config with behavior — split it.
- Max 300 lines per file. Max 30 lines per function. Max 5 parameters (use options object beyond that).
- Template literals embedding >20 lines of CSS, JS, or HTML must be extracted to separate files.
Open/Closed (OCP)
- Prefer data-driven designs over per-variant functions. Use config maps + one generic function instead of N nearly-identical functions.
- Use handler/strategy maps (
Record<EventType, Handler>) instead ofswitchstatements with >5 cases.
Liskov Substitution (LSP)
- Subclasses/implementations must honor the contract of their parent. Never override a method to throw "not supported" — redesign the hierarchy instead.
Interface Segregation (ISP)
- No
Record<string, unknown>,any, orobjectin public APIs. Define narrow, purpose-specific types. - Use TypeScript generics (
<T>) instead of loose types + inlineascasts.
Dependency Inversion (DIP)
- Import from barrel exports (
index.ts), not deep internal paths. Every public symbol must be re-exported from the package barrel. - Use static
importstatements. Never userequire()in TypeScript unless technically justified and documented. - Depend on abstractions (interfaces/types), not concrete implementations, when crossing module boundaries.
Separation of Concerns
- View layer: layout and event binding only. No business logic, no data fetching.
- Service layer: orchestration, external calls, state mutations.
- Data layer: queries, I/O, serialization. No UI references.
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 · 410 tokens per session scan A 9e9a6ae4b3e1
solid-architecture is a cursor rule published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 410 tokens to every session, about $0.0016 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.