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/ux-ui-product-experience)<a href="https://agentmods.dev/rules/jterratsdev/ableton-live-mcp/ux-ui-product-experience"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/ux-ui-product-experience/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/ux-ui-product-experience"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/ux-ui-product-experience.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.00641 | $0.00641 |
| Opus 5 | $0.00320 | $0.00320 |
| Sonnet 5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
ux-ui-product-experience 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 8d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX/UI Product Experience
User-facing work must be designed around real user flows, not isolated screens. Every interface must be usable, responsive, accessible, and clear for the intended audience.
Mobile First
- Design the smallest practical viewport first, then enhance for tablet and desktop.
- Primary actions must remain reachable on mobile without awkward scrolling or hidden controls.
- Text, buttons, forms, modals, menus, and navigation must not overflow or overlap at common mobile widths.
- Touch targets must be large enough for fingers and spaced to avoid accidental taps.
Responsive Behavior
- Define responsive layouts intentionally: stacking, wrapping, truncation, sticky areas, and overflow behavior must be planned.
- Test key screens at mobile, tablet, and desktop breakpoints before considering UI work complete.
- Avoid fixed-width layouts unless the format requires it. Use responsive constraints, flexible grids, and sensible max widths.
- Dynamic content, translated text, loading states, empty states, and error states must fit without breaking the layout.
User Flows
- Start UX work by identifying the end user, their goal, entry point, success path, failure path, and exit path.
- Do not optimize a screen while ignoring the full workflow before and after it.
- Every critical flow must include loading, empty, error, success, validation, and recovery states.
- Navigation should make the user's current location, available actions, and next step obvious.
UI Copy
- Use friendly, descriptive text that tells users what happened and what they can do next.
- Buttons should describe the action, not the implementation detail.
- Error messages must be specific, human-readable, and safe to show publicly.
- Tooltips should clarify unfamiliar icons, disabled controls, abbreviations, and advanced options.
Accessibility
- Preserve keyboard navigation, focus states, semantic structure, and readable contrast.
- Forms need labels, validation messages, and clear relationships between fields and errors.
- Do not rely on color alone to communicate status or severity.
- Motion and animation must not block comprehension and should respect reduced-motion preferences when the platform supports it.
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.
- 8d ago First seen · 52 lines · 641 tokens per session scan A 311a7f6d0fed
ux-ui-product-experience is a cursor rule published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 15d ago), licensed MIT. It adds 641 tokens to every session, about $0.0032 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
external-scale
Source: docs/agents/external-scale.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.
mobile-first-ui
Mobile-first UI for settings, dialogs, and lists — smaller type, stacked layouts, nested add dialogs.
frontend-design-direction
Derive a brief-specific visual direction, token sketch, hierarchy, and signature element.