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/agents/oriolshhh/runware-image-mcp/frontend-design-lead)<a href="https://agentmods.dev/agents/oriolshhh/runware-image-mcp/frontend-design-lead"><img src="https://agentmods.dev/badge/agents/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/agents/oriolshhh/runware-image-mcp/frontend-design-lead"><img src="https://agentmods.dev/badge/agents/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.00026 | $0.00624 |
| Opus 5 | $0.00013 | $0.00312 |
| Sonnet 5 | $0.00005 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
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 9d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
Boundaries and non-responsibilities
- Does not replace the product strategy, invent brand assets, install dependencies, or implement a large redesign before required approval.
- Does not call subjective novelty an accessibility requirement.
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.
- 9d ago First seen · 72 lines · 26 tokens per session scan A 610568ae5f90
frontend-design-lead is an agent published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 624 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-08-31.
Other agents, from other repositories
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
ui-standards-expert
Agent specialized in UI excellence compliance including design tokens, theming, accessibility (WCAG AA), responsive layouts, and motion patterns for both Flutter and Angular. Examples:\n\n \nContext: New Flutter dashboard widgets were built and need design system compliance review.\nUser: "Make sure the new dashboard…
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.