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/ai-assisted-developmentgit 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/ai-assisted-development)<a href="https://agentmods.dev/rules/jterratsdev/ableton-live-mcp/ai-assisted-development"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/ai-assisted-development.svg" alt="Measured on agentmods" 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 | $0.00655 | $0.00655 |
| Opus 5 | $0.00328 | $0.00328 |
| Sonnet 5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
ai-assisted-development 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-Assisted Development
AI-generated work must meet the same engineering bar as human-written work. Speed does not replace verification.
Grounding
- Inspect the existing codebase before proposing or editing code.
- Do not invent APIs, files, dependencies, commands, environment variables, or product requirements.
- When uncertain, state the assumption, verify locally, or ask the user before implementation.
- Prefer existing project patterns over generic generated patterns.
Implementation
- Keep AI-generated changes scoped to the agreed plan.
- Do not rewrite unrelated code, rename public APIs, or reformat broad areas without explicit need.
- Add tests and evidence for AI-generated behavior like any other change.
- Generated code must be understandable, maintainable, typed, and aligned with security rules.
Review
- Treat AI output as untrusted until reviewed.
- Check generated code for hallucinated imports, broken edge cases, security regressions, and excessive abstraction.
- Do not accept generated explanations as proof. Use tests, builds, type checks, docs, or runtime evidence.
- Record prompts, assumptions, or model-specific behavior when they materially affect product behavior or repeatability.
User Alignment
- Discuss the approach with the user before non-trivial AI-assisted implementation.
- Explain trade-offs clearly and identify risks introduced by generated code.
- If generated code reveals a better or riskier path than agreed, pause and realign before continuing.
Prompt Registry
- Use
.generated-prompts/as the durable prompt register for generated or substantially changed artifacts. - Before creating or substantially changing an artifact, read the relevant register file to preserve conventions, constraints, decisions, and known risks.
- After substantial changes, add or update one entry for the artifact with task, active role, key decisions, evidence, and the final prompt or a concise prompt summary.
- Keep only the latest prompt in each entry; rely on git history for prior versions. Do not update entries for typos, formatting-only edits, or single-line mechanical fixes.
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.
- 3d ago First seen · 54 lines · 655 tokens per session scan A b1109bfe1a50
ai-assisted-development is a cursor rule published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 10d ago), licensed MIT. It adds 655 tokens to every session, about $0.0033 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.