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 atezer/FMCP --skill audit-figma-design-systemgit clone --depth 1 https://github.com/atezer/FMCPWrote 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/atezer/fmcp/audit-figma-design-system)<a href="https://agentmods.dev/skills/atezer/fmcp/audit-figma-design-system"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/audit-figma-design-system/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/atezer/fmcp/audit-figma-design-system"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/audit-figma-design-system.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.00129 | $0.04675 |
| Opus 5 | $0.00064 | $0.02337 |
| Sonnet 5 | $0.00026 | $0.00935 |
| Haiku 4.5 | $0.00013 | $0.00468 |
Grade A, and why
audit-figma-design-system 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 8d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Figma Design System (tuval içi)
Kullanım (v3.1+): SADECE
fmcp-ds-audit-orchestratoralt-skill'i olarak çağrılır. Doğrudan entry point DEĞİL. Kullanıcı "audit et" dediğinde önce orchestrator yüklenir; orchestrator hangi audit tipini seçer (compliance / a11y / drift / visual_qa / impact).
Overview
Bu skill yalnızca okur; Figma node'unun yayınlanmış design system ile ne kadar entegre olduğunu yapısal kanıta dayanarak denetler. Görsel tatmin değil, instance / tekrar / ham değer / token bağlama odaklıdır.
Yazma gerekiyorsa aşağıdaki skill’lerden birine yönlendir.
F-MCP araç eşlemesi (resmi Figma MCP isimleri yerine)
| Niyet | F-MCP Bridge |
|---|---|
| Design context | figma_get_design_context |
| Görsel doğrulama | figma_capture_screenshot |
| Variable / bağlılık | figma_get_variables (verbosity=full), gerekiyorsa figma_get_styles |
| Yapı / iç içe instance haritası | figma_get_file_data (düşük depth), hedef node için figma_get_component veya figma_get_design_context; büyük tahta için figma_get_file_data (timeout riski — dikkat). Not: Bridge’te ayrı bir “yalnızca metadata” MCP aracı yok; yapı bu üç araçla alınır. |
| Kod/dev spec ipucu | figma_get_design_context (includeCodeReady=true); uygunsa figma_get_component_for_development |
| Kütüphanede aday bileşen | figma_search_components, özet için figma_get_design_system_summary |
F-MCP skill koordinasyonu
| Bulgu sonrası | Ne zaman |
|---|---|
| fix-figma-design-system-finding | Tek net bulgu, tek node veya dar küme |
| apply-figma-design-system | Çoklu bulgu, ekran geneli veya bölüm bölüm reconcile |
| design-token-pipeline | Rapor “token export / kod tarafı senkron” gerektiriyorsa |
| design-drift-detector | Aynı ekranın kod ile parity’si de soruluyorsa (Figma audit’ten sonra) |
| code-design-mapper | Eşleştirilecek bileşen aileleri netleştikten sonra mapping güncellemesi |
| figma-screen-analyzer | PO/PM/SEM'e yönelik teknik olmayan ekran analizi ve DS uyum raporu |
| ds-impact-analysis | Bir token/bileşen değişikliğinin etki yarıçapını ölçmek istiyorsan |
| ai-handoff-export / implement-design | Audit “Pass” veya düzeltme sonrası koda geçiş |
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.
- 8d ago First seen · 319 lines · 129 tokens per session scan A e2aaab34783c
audit-figma-design-system is a skill published in the GitHub repository atezer/FMCP (9 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 4,675 once invoked, about $0.0006 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
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…
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…
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…
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…
token-compliance
Check a codebase or implementation for token compliance — finding hardcoded values, wrong-tier token references, and inconsistent token application in consuming code. This checks how tokens are used in code, NOT how the tokens themselves are defined or structured. Trigger when someone says: are we using tokens…