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/qGolem/orcWrote 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/qgolem/orc/figma-design-sync)<a href="https://agentmods.dev/agents/qgolem/orc/figma-design-sync"><img src="https://agentmods.dev/badge/agents/qgolem/orc/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/qgolem/orc/figma-design-sync"><img src="https://agentmods.dev/badge/agents/qgolem/orc/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.00057 | $0.02272 |
| Opus 5.5 | $0.00023 | $0.00909 |
| Sonnet 5.5 | $0.00011 | $0.00454 |
| Haiku 4.5 | $0.00006 | $0.00227 |
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.
How it starts
The opening of the file, as written. The whole thing — 194 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.
- Accessibility (WCAG compliance, contrast ratios, focus indicators)
-
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 from CLAUDE.md
- 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 · 194 lines · 57 tokens per session scan A 2ac554a39268
figma-design-sync is an agent published in the GitHub repository qGolem/orc (5 stars, last pushed 7mo ago), licensed MIT. It adds 57 tokens to every session and 2,272 once invoked, about $0.0002 per session on Opus 5.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
evolve-frontend-design-review
Adversarial frontend design review agent for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build whenever scout.goaltype == "frontend-ui", to judge changed UI for production-grade design quality and BLOCK on design-system violations or broken responsive states.
ui-analyzer
Gathers decision-relevant UI facts from recorded external resources and the existing codebase. Use when frontend design needs compact evidence before UI Spec or Design Doc creation.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
tone
Design token engineering — token architecture, theming systems, style-dictionary pipelines.
design-expert
Use when: designing or auditing a design system, a marketing site, a web app screen, or an Apple-platform (iOS, iPadOS, macOS, watchOS, tvOS, visionOS) or Android mockup. Do NOT use for: wiring components into a codebase (delegate to the matching framework expert), or writing SwiftUI/Compose implementation code…
evolve-accessibility-audit
Accessibility audit agent for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after build whenever scout.goaltype == "accessibility" to adversarially review changed UI/HTML/React against WCAG 2.1/2.2 AA.