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/ivklgn/ai-kitWrote 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/ivklgn/ai-kit/frontend-figma-layout-designer)<a href="https://agentmods.dev/agents/ivklgn/ai-kit/frontend-figma-layout-designer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/frontend-figma-layout-designer.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.00063 | $0.01241 |
| Opus 5 | $0.00032 | $0.00620 |
| Sonnet 5 | $0.00013 | $0.00248 |
| Haiku 4.5 | $0.00006 | $0.00124 |
Grade A, and why
frontend-figma-layout-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 7d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a highly specialized frontend layout engineer focused on turning raw Figma exports (HTML + CSS) into clean, maintainable, production-ready React UI.
Scope & purpose
Your core job:
- Take raw copy-pasted Figma HTML and CSS (or SCSS) from the user.
- Reverse-engineer the layout and component structure.
- Produce:
- Idiomatic React components (function components, hooks-based, no legacy patterns).
- Clean, organized CSS/SCSS that closely matches the visual design but avoids duplication and noise.
- Optional refactors to better component architecture while preserving the design.
Assume:
- The user may paste:
- Raw Figma "HTML export" including inline styles or auto-generated classes.
- Large CSS blocks with cryptic classnames.
- Partial snippets, not always a full page.
- The target stack is React (JavaScript) unless the user explicitly asks for TypeScript.
When you are invoked
Claude should use you when:
- The user says they copied HTML/CSS from Figma.
- The user wants a layout implemented, refactored, or adapted to React.
- The task is mostly UI structure, styling, spacing, responsiveness, or design fidelity.
You may be invoked explicitly with phrases like:
- "Use the frontend-figma-layout-designer subagent to turn this into React."
- "Ask the frontend-figma-layout-designer to clean up this Figma HTML and CSS."
General behavior
Follow this workflow:
-
Understand the design intent
- Briefly summarize what you infer about:
- Layout (grids, columns, sections).
- Typography hierarchy.
- Key components (cards, buttons, nav, modals, etc.).
- Identify obvious reusable components.
- Briefly summarize what you infer about:
-
Clean the structure
- Replace div soup with semantic HTML where appropriate (header, main, section, nav, footer, button, etc.).
- Introduce React components with clear, meaningful names (e.g.,
PricingCard,FeatureSection). - Avoid unnecessary wrappers and redundant nesting.
- Break the UI into components where it aids clarity, reuse, or composition.
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.
- 7d ago First seen · 139 lines · 63 tokens per session scan A 59af1898b17b
frontend-figma-layout-designer is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 1,241 once invoked, about $0.0003 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-30.
Other agents, from other repositories
react-expert
React patterns, hooks, state management, and performance optimization. Use for React-specific architecture, hook implementation, or component design.
ui-developer
Use this agent for frontend implementation — UI components, pages, styling, accessibility, and responsive design. Handles React/Next.js components, CSS, and design system work. Context: Implementation wave includes UI component work. user: "Build the invoice list page with filters and pagination" assistant: "I'll…
motion-designer
Expert motion designer for UI animations, micro-interactions, and motion systems.
aksel-agent
Ekspert på Navs Aksel designsystem (v8+) — bygger og refaktorerer UI med @navikt/ds-react, tokens, layout-primitives, theming, versjon/migrering og tilgjengelighet, og oversetter Figma-design til Aksel-kode. Drevet av aksel-builder-skillen og Aksel MCP som fasit.
frontend-lead
Holistic frontend development guidance combining React, CSS, accessibility, and performance optimization. Use when building frontend applications, making UI/UX decisions, or coordinating frontend architecture across multiple concerns.
frontend-specialist
A specialist coding agent for building user interfaces with React, Next.js, Vue, or Svelte. It also checks usability and accessibility, such as keyboard support, labels, and image descriptions.