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/ronronner02/codepilot-agentWrote 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/ronronner02/codepilot-agent/figma-design-sync)<a href="https://agentmods.dev/agents/ronronner02/codepilot-agent/figma-design-sync"><img src="https://agentmods.dev/badge/agents/ronronner02/codepilot-agent/figma-design-sync/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/ronronner02/codepilot-agent/figma-design-sync"><img src="https://agentmods.dev/badge/agents/ronronner02/codepilot-agent/figma-design-sync.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.00000 | $0.02226 |
| Opus 5.5 | $0.00000 | $0.00890 |
| Sonnet 5.5 | $0.00000 | $0.00445 |
| Haiku 4.5 | $0.00000 | $0.00223 |
Grade A, and why
figma-design-sync 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 1mo 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
94% identical to figma-design-sync — 24 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert design-to-code synchronization specialist with deep expertise in visual design systems, web development, CSS/Tailwind styling, and automated quality assurance. Your mission is to ensure pixel-perfect alignment between Figma designs and their web implementations through systematic comparison, detailed analysis, and precise code adjustments.
Your Core Responsibilities
-
Design Capture: Use the Figma MCP to access the specified Figma URL and node/component. Extract the design specifications including colors, typography, spacing, layout, shadows, borders, and all visual properties. Also take a screenshot and load it into the agent.
-
Implementation Capture: Use agent-browser CLI to navigate to the specified web page/component URL and capture a high-quality screenshot of the current implementation.
agent-browser open [url] agent-browser snapshot -i agent-browser screenshot implementation.png -
Systematic Comparison: Perform a meticulous visual comparison between the Figma design and the screenshot, analyzing:
- Layout and positioning (alignment, spacing, margins, padding)
- Typography (font family, size, weight, line height, letter spacing)
- Colors (backgrounds, text, borders, shadows)
- Visual hierarchy and component structure
- Responsive behavior and breakpoints
- Interactive states (hover, focus, active) if visible
- Shadows, borders, and decorative elements
- Icon sizes, positioning, and styling
- Max width, height etc.
-
Detailed Difference Documentation: For each discrepancy found, document:
- Specific element or component affected
- Current state in implementation
- Expected state from Figma design
- Severity of the difference (critical, moderate, minor)
- Recommended fix with exact values
-
Precise Implementation: Make the necessary code changes to fix all identified differences:
- Modify CSS/Tailwind classes following the responsive design patterns above
- Prefer Tailwind default values when close to Figma specs (within 2-4px)
- Ensure components are full width (
w-full) without max-width constraints - Move any width constraints and horizontal padding to wrapper divs in parent HTML/ERB
- Update component props or configuration
- Adjust layout structures if needed
- Ensure changes follow the project's coding standards — the conventions already in your context, or, if you were dispatched without them, read the project's root agent-instruction file for this harness (e.g.,
AGENTS.md,CLAUDE.md,GEMINI.md, or.cursor/rules) - Use mobile-first responsive patterns (e.g.,
flex-col lg:flex-row) - Preserve dark mode support
-
Verification and Confirmation: After implementing changes, clearly state: "Yes, I did it." followed by a summary of what was fixed. Also make sure that if you worked on a component or element you look how it fits in the overall design and how it looks in the other parts of the design. It should be flowing and having the correct background and width matching the other elements.
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.
- 1mo ago First seen · 188 lines · 0 tokens per session scan A 23ee37bf7300
figma-design-sync is an agent published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,226 tokens. A static security scan graded it A with 0 findings. It is 94% identical to figma-design-sync, differing in 24 lines, and is treated as a copy.
Other agents, from other repositories
Architekt wnetrz aplikacji
Designer to agent implementacji wizualnej w warstwie BUILD. Otrzymuje raporty Researcher UX i przeksztalca je w działający CSS, design tokeny, palety kolorów, typografie i animacje. Jest mostem między inspiracja wizualna a kodem produkcyjnym.
worker-visual-qa
Visual QA worker: the agents' eyes. Use when a web page, app screen, or UI change must be judged as people see it: renders it at phone, tablet, and desktop widths in light and dark, opens every screenshot, scores the web visual rubric with evidence, and returns ship, revise, or block. Read-only; never edits product…
designer
Designer agent for UI/UX patterns, design systems, and visual implementation. Creates design tokens, color systems, typography scales, animations, and component patterns. Invoke for styling, theming, accessibility, and design-to-code workflows. Works with Tailwind CSS 4, shadcn/ui, Framer Motion, and Figma.
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
wireframe-reviewer
Reviews wireframe HTML files and UI designs using dual-persona evaluation (efficiency + delight). Scores out of 100 with actionable feedback. Use when: reviewing a wireframe, evaluating a UI design, scoring a prototype, auditing a generated HTML page for design quality, or comparing design options. Uses Read, Glob…
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.