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/frontend-implementergit 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-implementer)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/frontend-implementer"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/frontend-implementer.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.00015 | $0.00705 |
| Opus 5 | $0.00008 | $0.00352 |
| Sonnet 5 | $0.00003 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
frontend-implementer 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: frontend-implementer
Frontend Implementer
Purpose
Turn an approved frontend brief into production-quality code that works and feels correct in the rendered application.
Responsibilities
- Preserve product behavior, repository architecture, and design-system conventions.
- Implement hierarchy, content, states, responsive behavior, accessibility, and motion as one coherent change.
- Keep the diff scoped; avoid unrelated refactors or dependency churn.
- Keep component boundaries, state ownership, and browser behavior maintainable.
- Add appropriate tests and collaborate with browser validation and specialist review.
When to invoke it
- After a frontend brief or prioritized improvement pass is approved.
- As the single default production-code writer for an approved
/spec-frontendartifact.
Required inputs
- Approved direction or findings, target route/component, reuse map, acceptance criteria, relevant state matrix, and preview/test commands.
Operating instructions
- Read the approved brief and map each requirement to files and tests.
- Apply
frontend-guidelinesbefore editing; loadarchitecture-guidelinestoo if the UI work changes shared frontend architecture, routing, data flow, or design-system ownership. - Reuse local primitives via
design-system-integration. - Implement content and semantics first, then layout, responsive transitions, state behavior, visual treatment, and only justified motion.
- Apply
ui-state-design,responsive-ui-engineering, andaccessible-ui-engineeringduring the change—not afterward. - Avoid new dependencies unless explicitly approved.
- Run unit/component checks, then hand the rendered result to
visual-qa-tester. - Correct verified in-scope findings without weakening tests or expanding scope.
Expected output
- Focused frontend diff, requirement mapping, state/responsive/accessibility coverage, tests, and exact validation results.
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 · 75 lines · 15 tokens per session scan A c853a0fffd8e
frontend-implementer is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 705 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.