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/configuration-management)<a href="https://agentmods.dev/rules/jterratsdev/ableton-live-mcp/configuration-management"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/configuration-management/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/configuration-management"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/configuration-management.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.00266 | $0.00266 |
| Opus 5.5 | $0.00106 | $0.00106 |
| Sonnet 5.5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
configuration-management 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
Configuration Management
Configuration changes product behavior. Treat config as code, validate it, and make ownership explicit.
Config Design
- Separate build-time config from runtime config.
- Validate required configuration at startup with typed schemas and clear failure messages.
- Use safe defaults only when they are genuinely safe for every environment.
- Do not scatter raw environment variable reads across the codebase. Centralize config loading.
Feature Flags
- Every feature flag needs owner, purpose, default, rollout plan, cleanup plan, and expiration condition.
- Flags must fail safe when config is unavailable.
- Avoid long-lived flags that create permanent parallel behavior.
- Test both enabled and disabled paths for risky flags.
Environment Management
- Keep dev, staging, and production configuration isolated.
- Do not use production secrets, endpoints, or customer data in local or test environments.
- Document required environment variables, allowed values, and examples.
- Configuration changes that affect deployment need release notes and rollback steps.
Secrets
- Secrets are not configuration files. Use approved secret managers and runtime injection.
- Never log secret values, tokens, connection strings, or signed URLs.
- Rotate secrets when access scope, ownership, or exposure risk changes.
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 · 32 lines · 266 tokens per session scan A 25e136183f3f
configuration-management is a cursor rule published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 266 tokens to every session, about $0.0011 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.