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/documentation-standardsgit 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.00262 | $0.00262 |
| Opus 5 | $0.00131 | $0.00131 |
| Sonnet 5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
documentation-standards 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
Documentation Standards
Documentation is part of delivery when behavior, operation, or integration changes. Keep it close to the thing it explains.
Update Documentation When
- User-facing behavior, setup, configuration, API contracts, permissions, deployment, or operations change.
- A new workflow, feature flag, environment variable, dependency, migration, or integration is introduced.
- A bug fix changes expected behavior or removes a known limitation.
Minimum Artifacts
- README or getting-started docs for setup, local development, and common commands.
- API docs or contract examples for request, response, error, and auth changes.
- Runbooks for operational tasks, incidents, migrations, rollback, and manual support procedures.
- ADRs for important architecture choices.
- Release notes for user-visible changes, breaking changes, migrations, and known risks.
Quality Bar
- Documentation must be accurate, concise, and executable by someone who did not write the change.
- Include commands, environment variables, expected outputs, and troubleshooting notes when relevant.
- Do not duplicate source-of-truth configuration or type definitions in prose unless there is a sync check.
- Remove obsolete docs in the same change that makes them obsolete.
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 · 27 lines · 262 tokens per session scan A df7bb08d38de
documentation-standards is a cursor rule published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 9d ago), licensed MIT. It adds 262 tokens to every session, about $0.0013 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.