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 agentmods add skills/atezer/fmcp/generate-figma-screennpx skills add atezer/FMCP --skill generate-figma-screengit 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/generate-figma-screen)<a href="https://agentmods.dev/skills/atezer/fmcp/generate-figma-screen"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/generate-figma-screen.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.00118 | $0.15751 |
| Opus 5 | $0.00059 | $0.07876 |
| Sonnet 5 | $0.00024 | $0.03150 |
| Haiku 4.5 | $0.00012 | $0.01575 |
Grade A, and why
generate-figma-screen 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 5d 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 — 1,151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Figma Screen — Kod/Açıklamadan Figma Ekranı
Kullanım (v3.1+):
fmcp-screen-orchestratoraltında, Fast Path match FALSE olduğunda ana üretim motoru. Doğrudan entry point DEĞİL. Kullanıcı "ekran üret" dediğinde önce orchestrator yüklenir; orchestrator Fast Path match yapamadıysa buraya düşer.
Design Token Kuralı: Bu skill'deki kod örneklerinde geçen font adları, renk kodları, piksel boyutları yalnızca FORMAT gösterimidir. Çalışma anında tüm design token değerleri (font, renk, boyut, spacing, radius, gölge) kayıtlı kütüphaneden (
figma_get_variables,figma_get_styles) veya kullanıcıdan okunmalıdır. Hardcoded token değeri kullanma. Detay:project-context.md→ "Design Token Kuralı".
Overview
Bu skill, bir kod tabanından veya metin açıklamasından Figma'da tam sayfa/ekran oluşturur. Temel ilke: hardcode hex renk ve piksel değerleri yerine yayınlanmış design system bileşenlerini (component instance), değişkenlerini (variable) ve stillerini (text/effect style) kullanmak.
Topluluk figma-generate-design skill'inden uyarlanmış, F-MCP Bridge araçlarına göre yeniden yazılmıştır.
Zorunlu: Her figma_execute çağrısından önce figma-canvas-ops kılavuzundaki kuralları uygula.
Skill Boundaries
- Bu skill: Figma'da ekran oluşturma/güncelleme (DS bileşen instance'ları ile)
- Figma'dan kod üretmek istiyorsan → implement-design
- Yeniden kullanılabilir bileşen/variant oluşturmak istiyorsan → generate-figma-library
- Code Connect eşlemesi istiyorsan → code-design-mapper
Prerequisites
- F-MCP Bridge plugin bağlı olmalı
- Hedef Figma dosyasında yayınlanmış DS bileşenleri (veya team library erişimi) olmalı
- Kaynak: kod dosyaları veya ekran açıklaması
F-MCP skill koordinasyonu
- Önce (isteğe bağlı):
audit-figma-design-systemile mevcut ekranın DS uyumunu kontrol et - Birlikte:
figma-canvas-ops(herfigma_executeöncesi zorunlu) - Sonra:
figma-a11y-auditile erişilebilirlik kontrolü;design-drift-detectorile kod parity'si
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.
- 5d ago First seen · 1,151 lines · 118 tokens per session scan A 39bc366bb7af
generate-figma-screen is a skill published in the GitHub repository atezer/FMCP (9 stars, last pushed 1mo ago), licensed MIT. It adds 118 tokens to every session and 15,751 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…
codemod-generator
Generate codemods (automated code transformation scripts) for design system migrations — token renames, component API changes, prop deprecations, and import path updates. Produces ready-to-run jscodeshift or custom AST transform scripts that safely apply changes across consuming codebases. Trigger when someone says…