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 southleft/figma-console-mcp-skills --skill figma-check-design-paritygit clone --depth 1 https://github.com/southleft/figma-console-mcp-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/southleft/figma-console-mcp-skills/figma-check-design-parity)<a href="https://agentmods.dev/skills/southleft/figma-console-mcp-skills/figma-check-design-parity"><img src="https://agentmods.dev/badge/skills/southleft/figma-console-mcp-skills/figma-check-design-parity/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/southleft/figma-console-mcp-skills/figma-check-design-parity"><img src="https://agentmods.dev/badge/skills/southleft/figma-console-mcp-skills/figma-check-design-parity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00170 | $0.01000 |
| Opus 5 | $0.00085 | $0.00500 |
| Sonnet 5 | $0.00034 | $0.00200 |
| Haiku 4.5 | $0.00017 | $0.00100 |
Grade A, and why
figma-check-design-parity 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- check-design-parity-figma — 91% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
figma-check-design-parity — design vs code drift checker
Pull a Figma node's real specs and diff them against a codeSpec (what your implementation
actually renders). Returns a weighted parity score, per-property discrepancies with severity, and
suggested fixes. This is the inverse of code generation: get_design_context turns a design into
code; this skill confirms the code didn't drift away from the design.
All design reads go through use_figma, so it works on any Figma plan.
Skill boundaries
use_figmarules — load the officialfigma-useskill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-levelawait+return(no IIFE, nofigma.closePlugin();console.logis not returned), inputs inlined asconstat the top of each script, colors in 0–1 range, load fonts before any text op,await figma.getNodeByIdAsync(...), and atomic errors (a failed script applies nothing — read the error, fix, retry).- Generating code from a design → that's the native
get_design_context; this skill validates, not generates. - CODE-side a11y to feed
codeSpec.accessibility→ usefigma-scan-code-accessibility(--map-to-codespecemits exactly that object). - Design-side WCAG lint → use
figma-lint-design.
Workflow
- Assemble the codeSpec. Gather the values your component renders into the
codeSpecobject (references/parity-scoring.md has the full shape). You only need to fill the sections you want compared —visual,spacing,typography,accessibility. Tip:figma-scan-code-accessibility --map-to-codespecbuildscodeSpec.accessibilityautomatically. - Read the design specs. Set
NODE_IDand paste yourcodeSpecintoscripts/check-parity.js. Run it viause_figma(skillNames: "figma-check-design-parity"). It extracts the node's fills, strokes, corner radius, opacity, padding/gap, and text properties, then diffs them against the codeSpec. - Read the scorecard.
summary.parityScoreismax(0, 100 − (critical×15 + major×8 + minor×3 + info×1)).discrepancies[]lists each mismatch withcategory,property,severity,designValue,codeValue, and asuggestion. - Decide which side to fix. Each discrepancy says what design has vs what code has. Update code to
match the design, or push the design to match an intentional code change (via
figma-manage-variables/figma-use), then re-run to confirm the score rose.
What ships with it
2 files 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.
- 12d ago First seen · 48 lines · 170 tokens per session scan A f5ca87b31c74
figma-check-design-parity is a skill published in the GitHub repository southleft/figma-console-mcp-skills (81 stars, last pushed 26d ago), licensed MIT. It adds 170 tokens to every session and 1,000 once invoked, about $0.0009 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 skills, from other repositories
design-to-code
Use this skill when translating UI/UX designs into production-ready frontend code. Handles design source ingestion (Figma, Sketch, Adobe XD, screenshots, design specs), design token extraction, component hierarchy mapping, responsive breakpoint strategy, accessibility-first implementation (WCAG 2.1 AA minimum)…
design-md
Author/validate/export Google's DESIGN.md token spec files.
system-pitch
Write a design system investment pitch with a business case and ROI framing. Trigger when someone says: pitch the design system, make the case for the system, sell this to leadership, justify the investment, business case for design systems, why should we invest in a design system, or anything about building an…
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
ai-component-description
Generate AI-optimised text descriptions for components, formatted for Figma's MCP server and LLM consumption. This produces prose descriptions in a six-section format (purpose, props, anti-patterns, composition, accessibility, examples), NOT JSON schemas or structured data files. Trigger when someone says: write…
context-engine-builder
Generate a context engine — seven structured blueprint files (UX, UI, content, accessibility, ethical, technical, business intelligence) that encode everything an AI agent needs to work with a design system. This produces YAML infrastructure in .ai/context-engine/, NOT a health score or quality assessment. Trigger…