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/frontend-engineeringgit 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.00304 | $0.00304 |
| Opus 5 | $0.00152 | $0.00152 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
frontend-engineering 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 yesterday.
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
Frontend Engineering
Frontend code must keep user experience, state, accessibility, and maintainability aligned.
Architecture
- Separate presentation, state orchestration, data access, and domain logic.
- Keep components small and purpose-specific. Extract hooks, services, or view models when logic grows.
- Prefer existing design system components, tokens, and layout primitives over custom styling.
- Do not duplicate API types, validation schemas, or constants when they can be imported or generated.
State
- Separate local UI state from server/cache state.
- Keep state ownership close to the component or workflow that owns it.
- Avoid global state for data that is route-local, form-local, or derivable.
- Model loading, empty, error, success, stale, and optimistic states explicitly.
Forms
- Forms need labels, validation, helper text, disabled states, submission states, and recovery paths.
- Validate on the client for feedback and on the server for authority.
- Preserve user input when validation fails.
- Avoid destructive default actions and require confirmation for irreversible operations.
Accessibility & Responsive
- Preserve semantic HTML, keyboard navigation, focus states, readable contrast, and screen reader labels.
- Test common mobile, tablet, and desktop widths for user-facing flows.
- Do not hide required information behind hover-only interactions.
- Use tooltips for clarification, not as the only way to complete a task.
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.
- yesterday First seen · 33 lines · 304 tokens per session scan A 5720bee649d7
frontend-engineering is a cursor rule published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 8d ago), licensed MIT. It adds 304 tokens to every session, about $0.0015 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.