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-direction)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/frontend-design-direction"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/frontend-design-direction.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.1 | $0.00017 | $0.00532 |
| Opus 5 | $0.00009 | $0.00266 |
| Sonnet 5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
frontend-design-direction 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: frontend-design-direction
Frontend Design Direction
Purpose
Translate product intent and repository evidence into a coherent visual brief an implementer can follow without inventing taste mid-diff.
When to use it
- Before building a new user-facing surface or materially changing visual language.
Instructions
- State the target users, their primary task, the surface, constraints, and the requested degree of change. Ask only questions that alter the direction.
- Audit existing brand assets, tokens, components, typography, icons, content, and nearby screens. Label what must be preserved.
- If one aesthetic pack is enabled, read it as the primary voice. Do not blend conflicting primary packs; explain which one controls.
- Propose one direction, or two only when a real unresolved tradeoff exists.
- Define: design principles; information hierarchy; color roles; typography roles; spacing/density; radius/elevation; imagery/iconography; and motion tone.
- Sketch key layouts and responsive transitions using compact prose or ASCII.
- Name one signature element and justify it from the product—not fashion.
- List anti-goals and exact elements of the existing system to reuse.
- Review the direction for generic AI defaults, inconsistent personality, content mismatch, accessibility risk, and implementation cost.
Output format
A compact frontend brief: user/job, evidence, preservation constraints, chosen direction, tokens, type roles, layout, responsive behavior, states, signature, anti-goals, reused primitives, risks, and approval needs.
Anti-patterns
- Designing from an aesthetic adjective without product evidence.
- Replacing the local design system or brand by default.
- Presenting many moodboards to avoid making a recommendation.
- Treating a gradient, oversized heading, card grid, or animation as a concept.
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 · 53 lines · 17 tokens per session scan A c43b64bbf844
frontend-design-direction is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 532 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.
sidebar-webview-ui-ux
UI/UX standards for Akashi webviews (sidebar + panels).