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/responsive-ui-engineering)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/responsive-ui-engineering"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/responsive-ui-engineering/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/responsive-ui-engineering"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/responsive-ui-engineering.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.00020 | $0.00424 |
| Opus 5 | $0.00010 | $0.00212 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
responsive-ui-engineering 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.
What it actually says
Skill: responsive-ui-engineering
Responsive UI Engineering
Purpose
Make the interface adapt structurally rather than merely shrink between two screenshots.
When to use it
- For every new or materially changed user-facing layout.
Instructions
- Identify the content hierarchy and minimum viable space for each region.
- Use intrinsic layout, sensible min/max constraints, wrapping, and container behavior before adding breakpoints.
- Define how navigation, columns, tables, controls, overlays, and dense content reflow—not only their widths.
- Test representative narrow, medium, and wide viewports plus 200% zoom.
- Test long labels, localization expansion, empty values, large datasets, soft keyboard/touch behavior, and safe-area constraints when relevant.
- Preserve readable line lengths, touch targets, focus visibility, and logical DOM order at every layout.
- Capture evidence at the narrowest and widest supported states and at each structural transition.
Output format
A responsive contract: hierarchy, layout transitions, overflow behavior, viewport/content cases tested, failures found, and screenshots or observations.
Anti-patterns
- Desktop first followed by arbitrary media-query patching.
- Hiding required content on small screens without an equivalent path.
- Horizontal page scrolling, clipped focus rings, or visual order unlike DOM order.
Verification checklist
- No important content or action becomes unreachable, clipped, or ambiguous.
- Layout transitions follow content pressure and remain usable at zoom and with long text.
Apply
context-discoverybefore broad scanning: use a supplied context capsule first; otherwise check context frontmatter freshness, read.agent/context/routing.md, load only relevant summaries, and verify critical claims against source.
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 · 48 lines · 20 tokens per session scan A a00d1ddd8f38
responsive-ui-engineering is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 424 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
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.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
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.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.