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/oriolshhh/runware-image-mcp/design-system-integrationgit 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/design-system-integration)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/design-system-integration"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/design-system-integration.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.00014 | $0.00452 |
| Opus 5 | $0.00007 | $0.00226 |
| Sonnet 5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
design-system-integration 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: design-system-integration
Design System Integration
Purpose
Make new UI look native to the repository and avoid parallel token systems, duplicate primitives, and inaccessible custom controls.
When to use it
- Before implementing or redesigning any frontend component or screen.
Instructions
- Locate theme files, CSS variables, Tailwind/theme configuration, component libraries, typography, icons, layout primitives, stories, and UI tests.
- Build a reuse map: available tokens/components, their supported states, and the closest precedent for the requested UI.
- Reuse semantic tokens rather than raw values. Reuse accessible primitives
rather than recreating behavior from
divelements. - Extend only when no existing abstraction fits. Prefer the smallest semantic addition and document its intended reuse.
- Preserve framework, styling method, naming, import boundaries, server/client conventions, and theming behavior.
- Check light/dark/high-contrast themes and localization when the repository supports them.
- Require approval before adding a UI, icon, animation, or styling dependency.
Output format
A reuse map plus implementation decisions: reused primitives, extended tokens, new abstractions with justification, affected themes, and rejected dependencies.
Anti-patterns
- Hard-coded colors and spacing beside an existing token system.
- A second Button, Modal, or Form abstraction with nearly identical behavior.
- Installing a library because a reference skill mentioned it.
- Hand-building complex accessible controls when a local primitive exists.
Verification checklist
- New UI uses the repository's public frontend patterns and supported themes.
- Every new token/component/dependency has a demonstrated gap and narrow scope.
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.
- 2d ago First seen · 50 lines · 14 tokens per session scan A 09d3b2bdc9cf
design-system-integration is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 452 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
本规范定义了使用 shadcn/ui 和 Tailwind CSS 开发新组件的标准流程和最佳实践。.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
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.