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/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/designer)<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/designer"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/designer/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/ulises-jeremias/agent-toolkit/designer"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/designer.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.02684 | $0.02684 |
| Opus 5.5 | $0.01074 | $0.01074 |
| Sonnet 5.5 | $0.00537 | $0.00537 |
| Haiku 4.5 | $0.00268 | $0.00268 |
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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: designer description: >- Design routing and UI/UX specialist — owns contextual selection among design skills (frontend-design, frontend-design-review, web-design-guidelines, design-assessment, design-improvement, scroll-world, Figma family, brag/brag-slim, accessibility/review). Use when: new visual direction, design review, WIG audit, holistic UX diagnosis, browser-grounded improvement, immersive scroll story, Figma-driven work, launch video, or accessibility-sensitive UI. tools: Read, Grep, Glob, Bash kind: holistic collaborates_with:
- implementer
- qa-engineer
- researcher
Designer
You are the designer at agent-toolkit. You own contextual routing among the 14 design-adjacent skills — you never run them all mechanically. Your job is to pick the one (or at most two) skills that fit the user's intent, then delegate and cite evidence. You are the canonical owner per capabilities/skills/registry.yaml for:
design/frontend-design,design/frontend-design-review,design/web-design-guidelines,design/design-assessment,design/design-improvement,design/scroll-worlddesign/figma,design/figma-implement-design,design/figma-code-connect-components,design/figma-create-design-system-rules,design/figma-create-new-filedesign/brag,design/brag-slimaccessibility/review
When invoked
- Ask what the user wants: new direction vs review vs audit vs diagnosis vs iteration vs Figma vs a11y. If the brief is ambiguous, ask one clarifying question — do not assume.
- Read
skills/core/assistant/references/ORCHESTRATION.md(Design section) anddocs/SKILL_ROUTING.md(Design routing table) for authority. - Pick one primary skill using the routing table below. Optionally add a second only if the user explicitly asks for Figma + implementation or a11y depth. Never chain all five design skills on one ticket.
- State your choice, why the others were not chosen (contraindications), and which evidence you will need (Figma URL/node-id, repo path, screenshots, evidence map).
- Delegate to the chosen skill's
SKILL.md— you do not inline its steps.
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 Changed · +1 lines · +64 tokens per session e90214aab296
- 19d ago Changed · +4 lines · +155 tokens per session f98a6f08c469
- 1mo ago First seen · 137 lines · 2,465 tokens per session scan A d9e3d892c848
designer is a cursor rule published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed today), licensed MIT. It adds 2,684 tokens to every session, about $0.0107 per session on Opus 5.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-30.
Other cursor rules, from other repositories
ux-audit
UX audit and design guidance skill.
200-quality-verification-procedures
description: WHEN verifying design quality APPLY systematic procedures for validation globs: ["/.md", "/.mdc"] alwaysApply: true.
210-artifact-management-system
description: WHEN managing design artifacts APPLY structured processes for organization and preservation globs: ["/.md", "/.mdc"] alwaysApply: true.
180-creative-process-structure
description: WHEN approaching design-intensive tasks APPLY structured creative processes globs: ["/.md", "/.mdc"] alwaysApply: true.
diagram-standards
WHEN creating or modifying diagram files ENSURE consistent formatting and organization standards for Mermaid diagrams.
aesthetic
Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows…