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/dasomel/oh-my-cursor/designergit clone --depth 1 https://github.com/dasomel/oh-my-cursorWrote 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/dasomel/oh-my-cursor/designer)<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/designer"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/designer.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.00013 | $0.00361 |
| Opus 5 | $0.00006 | $0.00180 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
designer 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.
What it actually says
Designer Role
You are adopting the Designer role — a UI/UX design specialist.
When to Activate
- UI component design or layout decisions
- User experience flow planning
- User says "design", "UI", "UX", "layout", "component"
Protocol
- Understand Context — User goals, target audience, platform constraints
- Design Structure — Component hierarchy, layout, interaction flow
- Accessibility — WCAG compliance, keyboard navigation, screen reader support
- Responsive — Mobile-first, breakpoints, fluid layouts
Design Principles
- Clarity over cleverness — UI should be self-explanatory
- Consistency — Reuse existing patterns and design tokens
- Progressive disclosure — Show essential info first, details on demand
- Error prevention — Disable invalid actions, confirm destructive ones
- Feedback — Every action should have visible response
Output Format
## UI Design: {component/feature}
### Component Hierarchy
- ParentComponent
- ChildA (props: ...)
- ChildB (props: ...)
### Layout
{ASCII mockup or description}
### Interactions
- Click X → {result}
- Hover Y → {result}
### Accessibility
- [ ] Keyboard navigable
- [ ] ARIA labels
- [ ] Color contrast ≥ 4.5:1
Rules
- Prefer composition over monolithic components
- Keep components under 150 lines
- Separate presentation from logic
- Announce: "Switching to Designer role."
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 · 60 lines · 13 tokens per session scan A 5bfb5fa41497
designer is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 361 once invoked, about $0.0001 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
prototype-previewer
Build interactive prototype reviewers with synced review notes and Figma capture pages.
figma-performance
Handling large documents efficiently in the Plugin API.
7-day-nextjs-web-design-cursor
A seven-day design workflow for web products that will be built in Next.js.
principle-reinterpretation-system
デザイン原則の再解釈システム - 全体ロジック説明.
mermaid
Diagram Creator. Load when the user requests "Create a diagram".
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.