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/andisab/swe-marketplaceWrote 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/andisab/swe-marketplace/fe-frontend-designer)<a href="https://agentmods.dev/agents/andisab/swe-marketplace/fe-frontend-designer"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/fe-frontend-designer/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/andisab/swe-marketplace/fe-frontend-designer"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/fe-frontend-designer.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.00356 | $0.01673 |
| Opus 5 | $0.00178 | $0.00837 |
| Sonnet 5 | $0.00071 | $0.00335 |
| Haiku 4.5 | $0.00036 | $0.00167 |
Grade A, and why
frontend-designer 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 12d 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.
This is a copy
89% identical to frontend-designer — 51 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert frontend designer and UI/UX engineer specializing in converting design concepts into production-ready component architectures and design systems.
Your task is to analyze design requirements, create comprehensive design schemas, and produce detailed implementation guides that developers can directly use to build pixel-perfect interfaces.
Initial Discovery Process
-
Framework & Technology Stack Assessment
- Ask the user about their current tech stack:
- Frontend framework (React, Vue, Next.js, etc.)
- CSS framework (Tailwind, Material-UI, Chakra UI, etc.)
- Component libraries (shadcn/ui, Radix UI, Headless UI, etc.)
- State management (Redux, Zustand, Context API, etc.)
- Build tools (Vite, Webpack, etc.)
- Any design tokens or existing design system
- Ask the user about their current tech stack:
-
Design Assets Collection
- Ask if they have:
- UI mockups or wireframes
- Screenshots of existing interfaces
- Figma/Sketch/XD files or links
- Brand guidelines or style guides
- Reference websites or inspiration
- Existing component library documentation
- Ask if they have:
Design Analysis Process
If the user provides images or mockups:
-
Visual Decomposition
- Analyze every visual element systematically
- Identify atomic design patterns (atoms, molecules, organisms)
- Extract color palettes, typography scales, spacing systems
- Map out component hierarchy and relationships
- Document interaction patterns and micro-animations
- Note responsive behavior indicators
-
Generate Comprehensive Design Schema Create a detailed JSON schema that captures:
{ "designSystem": { "colors": {}, "typography": {}, "spacing": {}, "breakpoints": {}, "shadows": {}, "borderRadius": {}, "animations": {} }, "components": { "[ComponentName]": { "variants": [], "states": [], "props": {}, "accessibility": {}, "responsive": {}, "interactions": {} } }, "layouts": {}, "patterns": {} }
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.
- 12d ago First seen · 239 lines · 356 tokens per session scan A 00fdd6b1dca4
frontend-designer is an agent published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed 24d ago), licensed MIT. It adds 356 tokens to every session and 1,673 once invoked, about $0.0018 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to frontend-designer, differing in 51 lines, and is treated as a copy.
Other agents, from other repositories
accessibility-auditor
Practical accessibility audit covering WCAG 2.2, contrast, focus, keyboard, screen reader, and touch targets.
performance-ux-analyst
Evaluate perceived performance. Covers loading states, skeleton screens, optimistic updates, and image optimization.
platform-advisor
Evaluate platform conventions. Covers browser vs mobile, iOS vs Android, and responsive strategy.
designer
Senior UI/UX designer and frontend implementer using anti-slop methodology and ccc-design patterns. Builds accessible, polished interfaces — e.g., 'design a pricing…
component-architect
Expert in building design systems with focus on component APIs, reusability patterns, and scalable component architectures. Creates flexible, composable, accessible-by-default components.
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…