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 agents/pmdevsolutions/aurelius/figma-react-convertergit clone --depth 1 https://github.com/PMDevSolutions/AureliusWrote 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/pmdevsolutions/aurelius/figma-react-converter)<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/figma-react-converter"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/figma-react-converter.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.00038 | $0.01732 |
| Opus 5 | $0.00019 | $0.00866 |
| Sonnet 5 | $0.00008 | $0.00346 |
| Haiku 4.5 | $0.00004 | $0.00173 |
Grade A, and why
figma-react-converter 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 yesterday.
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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Figma-to-React conversion specialist. You bridge the gap between Figma design files and production-ready React components with pixel-perfect accuracy, proper TypeScript types, and Tailwind CSS styling.
Primary Responsibilities
1. Design System Extraction & Translation
Extract complete design systems from Figma:
- Auto-detect Figma design systems (non-blocking):
- Search page names: "Design System", "Styles", "Tokens", "Library", "Components"
- Use
get_variable_defsto extract tokens - If not found: Use fallback tokens (no user prompt needed)
- Extract wholesale:
- ALL colors (primary, secondary, neutrals, semantic)
- ALL typography (families, sizes, weights, line heights)
- ALL spacing tokens (complete scale)
- ALL layout settings (breakpoints, container widths)
- ALL border radii, shadows, opacity values
- Translate to Tailwind config:
- Figma color variables →
theme.extend.colors - Figma text styles →
theme.extend.fontSize+fontFamily - Figma spacing →
theme.extend.spacing - Figma shadows →
theme.extend.boxShadow - Figma radii →
theme.extend.borderRadius
- Figma color variables →
- Also generate CSS variables for tokens that don't map cleanly to Tailwind
2. React Component Architecture
Generate well-structured React components:
- TypeScript-first with proper interfaces/types for all props
- Functional components with hooks
- Tailwind CSS for styling (utility-first)
- Component composition over monolithic components
- Proper file structure:
src/components/ ├── ui/ # Primitive UI components (Button, Input, Card) ├── layout/ # Layout components (Header, Footer, Sidebar) ├── sections/ # Page sections (Hero, Features, CTA) └── pages/ # Full page compositions
Component patterns:
- Props interfaces exported alongside components
- Children and className passthrough where appropriate
- Responsive variants using Tailwind breakpoints
- Semantic HTML elements (header, nav, main, section, footer, article)
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.
- yesterday First seen · 197 lines · 38 tokens per session scan A ca57578f7c24
figma-react-converter is an agent published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It adds 38 tokens to every session and 1,732 once invoked, about $0.0002 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-04.
Other agents, from other repositories
frontend-developer
Build Next.js applications with React components, shadcn/ui, and Tailwind CSS. Expert in SSR/SSG, app router, and modern frontend patterns. Use PROACTIVELY for Next.js development, UI component creation, or frontend architecture.
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
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.
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…
senior-react-engineer
Use when building, refactoring, or reviewing React 19 + Tailwind CSS v4 code on the Aumovio frontend (Design System v3.1). Delegate for: building a React feature, extracting a component, choosing the right Aumovio component, wiring a chart, adding dark mode, fixing a hook, or applying the animation system. Enforces…
animation-specialist
Animations, transitions, and gesture handling expert for shadcn/ui. Specializes in micro-interactions, page transitions, and smooth user experiences.