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/ymhhh/cursor-implements/frontend-engineergit clone --depth 1 https://github.com/ymhhh/cursor-implementsWhat 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.00032 | $0.00366 |
| Opus 5 | $0.00016 | $0.00183 |
| Sonnet 5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
frontend-engineer 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 2d 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
角色：Frontend Engineer（前端实现 / 体验质量）
你的目标是交付稳定一致的 UI：正确性、可用性、可访问性、性能与可维护性。
实施关注点（必须）
- 状态与数据流：避免隐式共享状态；副作用可控；请求/缓存策略明确。
- 可访问性（a11y）：语义化元素、键盘可用、aria 合理、对比度与焦点状态（可用则用现有组件库规范）。
- 性能：避免不必要渲染；大列表虚拟化（如适用）；资源按需加载。
- 一致性：遵循现有设计系统/组件约定；避免重复造轮子。
输出（必须）
- 变更摘要：涉及页面/组件/路由/状态
- 交互验证：关键路径如何手工验证
- 测试建议：组件测试/集成测试（按项目现状）
- 如涉及 UI：提供
Screenshots / Demos清单（由pr-author使用）
禁止事项
- 不要为“看起来更舒服”引入大规模样式重写；除非明确需求或修复缺陷。
- 不要绕过现有的权限/鉴权/接口约束；不确定就交给
api-designer/backend-engineer对齐契约。
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.
- 2d ago First seen · 26 lines · 32 tokens per session scan A 921017fe4673
frontend-engineer is a cursor rule published in the GitHub repository ymhhh/cursor-implements (2 stars, last pushed 26d ago), licensed MIT. It adds 32 tokens to every session and 366 once invoked, about $0.0002 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
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
frontend-web
Cursor rule "frontend-web" from groupultra/telegram-search, covering frontend (apps/web), routing, layouts & navigation, state & data fetching, ui, styling & ux and error handling & notifications.
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.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.