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 skills add memi-design/design-skills --skill figma-syncgit clone --depth 1 https://github.com/memi-design/design-skillsWrote 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/skills/memi-design/design-skills/figma-sync)<a href="https://agentmods.dev/skills/memi-design/design-skills/figma-sync"><img src="https://agentmods.dev/badge/skills/memi-design/design-skills/figma-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/skills/memi-design/design-skills/figma-sync"><img src="https://agentmods.dev/badge/skills/memi-design/design-skills/figma-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.00026 | $0.01162 |
| Opus 5 | $0.00013 | $0.00581 |
| Sonnet 5 | $0.00005 | $0.00232 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
figma-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 10d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma Sync Patterns — Memoire Connect Skill
Orchestrates reliable bidirectional sync between Figma and the local codebase through the Memoire bridge.
Sync Modes
1. Pull Sync (Figma to Code)
Trigger: memi pull, document-changed event, or manual
Pipeline:
Figma Plugin
-> getVariables + getComponents + getStyles (parallel)
-> Parse raw data to DesignSystem
-> Diff against existing registry
-> Update changed tokens/components only
-> Auto-spec new components
-> Regenerate affected specs
Incremental strategy:
- Compare token values by name + collection — only update changed
- Compare components by
figmaNodeId— detect added/removed/modified - Track
lastSynctimestamp to skip unchanged files
2. Push Sync (Code to Figma)
Trigger: memi sync --push, agent canvas operations
Pipeline:
Local Specs + Tokens
-> Diff against Figma state
-> Generate Figma Plugin API calls
-> Execute via bridge
-> Self-heal (screenshot + verify)
-> Update Code Connect mappings
Safety rules:
- Never overwrite Figma components that have been modified since last pull
- Prompt user if Figma-side changes detected since last sync
- Use
figma.currentPage.findOne()to target specific nodes, not blind creation
3. Bidirectional Merge
When both sides have changes:
| Scenario | Resolution |
|---|---|
| Token value changed in Figma only | Accept Figma |
| Token value changed in code only | Push to Figma |
| Both changed same token | Prompt user — show diff |
| New component in Figma | Pull + auto-spec |
| New spec in code | Push to Figma on next sync |
| Component deleted in Figma | Flag in CLI, don't auto-delete spec |
| Spec deleted locally | Flag, don't auto-delete in Figma |
Change Detection
Token Diffing
interface TokenDiff {
added: DesignToken[];
removed: DesignToken[];
modified: { before: DesignToken; after: DesignToken }[];
unchanged: number;
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 160 lines · 26 tokens per session scan A c3ece80f76b3
figma-sync is a skill published in the GitHub repository memi-design/design-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 1,162 once invoked, about $0.0001 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-31.
Other skills, from other repositories
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
motion-lexicon
Design, build, compose, implement, review, and contribute polished product interfaces with Motion Lexicon components and motion primitives. Use this skill when a user asks for a complete React page, landing page, dashboard, settings screen, or product surface in the Motion Lexicon visual language; asks what motion…
motion-craft
Use when an interface moves and the movement has to feel right — durations and easing, what must never animate, fixing motion that reads sluggish, cheap or janky, and reduced-motion. Web and native. NOT the visual system (that is design), NOT the graded critique (that is design-loop).
design-engineering
Premium design engineering skill for agentic workflows — produces high-end, distinctive UI designs using DESIGN.md as the portable contract across Pencil MCP (in-IDE canvas), Figma MCP (team handoff + design tokens), and Google Stitch (vibe exploration + AI generation). Enforces anti-generic principles, WCAG 2.2 AA…
motion-foundations
Motion tokens, spring presets, performance rules, device adaptation, accessibility enforcement, and SSR safety for React / Next.js using motion/react. Foundation layer — all other motion skills depend on this.
motion-guide
Use when designing, adding, changing, suggesting, or reviewing UI motion. Motion Guide is a default-trigger motion decision advisor for AI coding agents: it decides whether motion should exist, selects an appropriate functional or expressive pattern, and constrains implementation with timing, easing, accessibility…