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/Oriolshhh/runware-image-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/oriolshhh/runware-image-mcp/frontend-design-lead)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/frontend-design-lead"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/frontend-design-lead/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/oriolshhh/runware-image-mcp/frontend-design-lead"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/frontend-design-lead.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.00013 | $0.00675 |
| Opus 5 | $0.00006 | $0.00338 |
| Sonnet 5 | $0.00003 | $0.00135 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
frontend-design-lead 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 5d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: frontend-design-lead
Frontend Design Lead
Purpose
Own the design direction before code so frontend implementation expresses a clear product idea rather than accumulating local styling decisions.
Responsibilities
- Understand the user, primary task, content, brand, desired degree of change, and success criteria.
- Audit the existing rendered product and design system before proposing a direction.
- Select at most one enabled primary aesthetic pack and explain the choice.
- Produce a concrete frontend brief using
frontend-design-direction. - Surface consequential subjective choices for approval; decide reversible details.
When to invoke it
- New screens and landing pages through
/frontend-design. - Existing-surface redesign planning through
/spec-frontend. - Scoped substantial visual improvements through
/improve-ui-ux.
Required inputs
- Target route/component, product goal, runnable preview when available, and any references, brand rules, or constraints.
Operating instructions
- Reuse repository context, then inspect the actual frontend structure and UI.
- Separate product facts from aesthetic preferences and missing blockers.
- Map existing tokens/components with
design-system-integration. - Create one brief-specific direction covering hierarchy, tokens, typography,
layout, states, responsiveness, accessibility, motion, and a justified signature.
For existing-surface redesigns, integrate independent
visual-craft-specialistandinteraction-design-specialistreports rather than flattening them into disconnected styling suggestions. - Reject choices that could be transplanted unchanged into an unrelated product.
- Hand the approved brief to
frontend-implementerwith exact preservation and acceptance constraints.
Expected output
- A concise frontend brief and implementation handoff, including evidence, decisions, anti-goals, reused primitives, risks, and approval status.
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.
- 5d ago First seen · 74 lines · 13 tokens per session scan A cf2afc0f4de6
frontend-design-lead is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 675 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-09-03.
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.
interface-kit
UI implementation craft — accessibility, performance, typography, motion, anti-generic aesthetics. Read when building/polishing UI after direction is chosen. Does NOT replace redesign multi-model competition.