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 apply-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/apply-figma-design-system)<a href="https://agentmods.dev/skills/atezer/fmcp/apply-figma-design-system"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/apply-figma-design-system.svg" alt="Measured on agentmods" 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.00116 | $0.01982 |
| Opus 5 | $0.00058 | $0.00991 |
| Sonnet 5 | $0.00023 | $0.00396 |
| Haiku 4.5 | $0.00012 | $0.00198 |
Grade A, and why
apply-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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Figma Design System (geniş yazma)
Overview
Mevcut bir frame/page published design system kullanmalıdır; detached layer, yerel wrapper ve tek seferlik kompozisyonlar hedeflenir.
Tek dar bulgu için fix-figma-design-system-finding kullan; bu skill çok bölüm ve koordineli reconcile içindir.
Giriş Modları
Bu skill iki farklı modda çalışabilir:
- review-then-apply (varsayılan) — Tam audit → envanter → bölüm sınıflandırması → onay → uygulama. İlk kez DS hizalaması yapılıyorsa veya kapsamlı tarama istendiğinde kullanılır.
- apply-known-scope — Kullanıcı hedef frame'leri ve stratejiyi zaten biliyorsa (ör. önceki audit'ten), audit adımları atlanır ve doğrudan uygulama başlar. Giriş:
{ frames: [{ id: "72:293", strategy: "exact-swap" | "compose-from-primitives" }] }.
Mod, kullanıcı girdisinden otomatik çıkarılır: frame ID + strateji belirtilmişse apply-known-scope, aksi halde review-then-apply.
%80 Uyum Eşiği
Bölüm sınıflandırması sonrası uyum oranı hesaplanır:
uyumOranı = (already-connected + exact-swap + compose-from-primitives) / toplamBölüm
uyumOranı >= 0.80: Otomatik uygulama önerilir.uyumOranı < 0.80: Uyarı gösterilir — "67% (16/24) otomatik düzeltilebilir. Minimum %80 önerilir. Devam edilsin mi?" Kullanıcı onay vermeden uygulama başlamaz.
Bölüm sınıflandırması
Her bölüm tam olarak biri:
already-connected— Zaten kütüphane instance veya kullanıcıca kabul görmüş kompozisyonexact-swap— Tek bir library component/variant ile doğrudan değiştirilebilircompose-from-primitives— Tek composite yok; yayınlanmış primitive’lerle yeniden kurulurblocked— Kütüphane yok, import başarısız veya kasıtlı bespoke
F-MCP araç eşlemesi
| Niyet | F-MCP Bridge |
|---|---|
| Özet / sayfa yapısı | figma_get_file_data, figma_get_design_system_summary |
| Görsel | figma_capture_screenshot |
| Yapı envanteri | figma_get_file_data, figma_get_design_context, figma_execute (instance → mainComponent keşfi) |
| Aday bileşen | Önce aynı dosyadaki referans ekranlar; sonra figma_search_components |
| Token | figma_get_variables, figma_get_styles |
| Yazma | figma_execute |
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 · 142 lines · 116 tokens per session scan A f8b8a252b7d1
apply-figma-design-system is a skill published in the GitHub repository atezer/FMCP (9 stars, last pushed 1mo ago), licensed MIT. It adds 116 tokens to every session and 1,982 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…
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…
accessibility-per-component
Run an accessibility audit on a specific design system component. Trigger when someone says: accessibility check, a11y audit, WCAG compliance, is this accessible, check accessibility, does this meet WCAG, screen reader support, keyboard navigation check, or anything about auditing the accessibility of a specific…
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…