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/figma-screen-analyzernpx skills add atezer/FMCP --skill figma-screen-analyzergit 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/figma-screen-analyzer)<a href="https://agentmods.dev/skills/atezer/fmcp/figma-screen-analyzer"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/figma-screen-analyzer.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 | $0.00135 | $0.02646 |
| Opus 5 | $0.00068 | $0.01323 |
| Sonnet 5 | $0.00027 | $0.00529 |
| Haiku 4.5 | $0.00014 | $0.00265 |
Grade A, and why
figma-screen-analyzer 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma Screen Analyzer — UI Analiz Raporu
Overview
Bu skill, Figma ekranını teknik olmayan dilde analiz ederek PO, PM ve SEM'ler için anlaşılır bir rapor üretir. DS uyum oranı, bileşen envanteri, görsel hiyerarşi değerlendirmesi ve aksiyon önerileri içerir.
Salt okunur — Figma tuvalinde değişiklik yapmaz.
Prerequisites
- F-MCP Bridge plugin bağlı olmalı
- Hedef ekranın node ID'si veya URL'i bilinmeli
F-MCP skill koordinasyonu
- İlişkili:
audit-figma-design-system(teknik DS denetimi — bu skill'in PO/PM versiyonu) - Sonra: Bulgulara göre
apply-figma-design-systemveyaai-handoff-exportönerilir - Karşılaştırma: İki ekran karşılaştırması için her ikisine de ayrı analiz yapılır
Required Workflow
Step 1: Plugin Bağlantısını Doğrula
figma_get_status()
Step 2: Ekran Verisi Topla
DERİN ANALİZ KURALI: Sadece frame/node isimlerine bakarak sonuç çıkarma. Her node'un içindeki text content (
characters), instance prop'ları ve child yapılarını detaylı oku. Bir şeyin "eksik" veya "yok" olduğunu iddia etmeden önce tüm child node'ların içeriğini kontrol et.
GÖRSEL DOĞRULAMA KURALI: Analiz sonucunu raporlamadan önce
figma_capture_screenshotile ekran görüntüsü al ve görsel olarak kontrol et. Text content ile screenshot'ın tutarlı olduğunu teyit et. Çelişki varsa screenshot'ı esas al.
figma_get_design_context(
nodeId="<NODE_ID>",
depth=3,
verbosity="full",
includeLayout=true,
includeVisual=true,
includeTypography=true
)
figma_capture_screenshot(nodeId="<NODE_ID>")
Step 3: İlk İzlenim Analizi (2 Saniye Testi)
Screenshot'a bakarak hızlı sezgisel değerlendirme yap (DS metriklerinden ÖNCE):
- Göz çekimi: İlk bakışta göz nereye gidiyor? Bu doğru öğe mi? (CTA, başlık, hero görsel?)
- Duygusal tepki: Ekran güven mi, kafa karışıklığı mı, heyecan mı uyandırıyor?
- Amaç netliği: Ekranın ne için olduğu 2 saniyede anlaşılıyor mu?
- Görsel yoğunluk: Sıkışık mı, dengeli mi, çok boş mu?
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 · 244 lines · 135 tokens per session scan A e226427bda70
figma-screen-analyzer is a skill published in the GitHub repository atezer/FMCP (9 stars, last pushed 1mo ago), licensed MIT. It adds 135 tokens to every session and 2,646 once invoked, about $0.0007 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…
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…
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-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…