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 agentmods add rules/jterratsdev/ableton-live-mcp/dependency-managementgit clone --depth 1 https://github.com/jterratsdev/ableton-live-mcpWhat 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 | $0.00311 | $0.00311 |
| Opus 5 | $0.00156 | $0.00156 |
| Sonnet 5 | $0.00062 | $0.00062 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
dependency-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 2d 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
Dependency Management
Dependencies are part of the product attack surface and runtime behavior. Treat them as code.
Adding Dependencies
- Prefer the standard library or existing project dependencies before adding a new package.
- Justify every new runtime dependency with purpose, maintenance status, license, security posture, and alternatives considered.
- Do not add dependencies for trivial utilities that can be implemented safely in a few lines.
- Avoid packages with low maintenance, unclear ownership, known malware history, or broad install scripts.
Versioning
- Pin dependency versions through lockfiles and commit lockfile updates with the package manifest.
- Do not manually edit lockfiles unless the package manager requires it and the change is reviewed.
- Major upgrades require changelog review, migration notes, test evidence, and rollback considerations.
- Keep dependency updates atomic unless a coordinated upgrade is required.
Supply Chain Security
- Run dependency scanning in CI and block critical or high vulnerabilities unless risk-accepted.
- Never run unvetted package execution commands in CI.
- Review transitive dependency risk when adding security-sensitive, build, auth, crypto, or deployment tooling.
- Remove unused dependencies promptly.
Automation
- Use Dependabot, Renovate, or equivalent for routine updates where possible.
- Group low-risk patch updates, but keep major and security updates separate.
- Security updates must include the vulnerability identifier, affected package, fixed version, test evidence, and any compensating controls.
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.
- 2d ago First seen · 32 lines · 311 tokens per session scan A d58347655403
dependency-management is a cursor rule published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 9d ago), licensed MIT. It adds 311 tokens to every session, about $0.0016 per session on Opus 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
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.