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 figma-a11y-auditgit 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-a11y-audit)<a href="https://agentmods.dev/skills/atezer/fmcp/figma-a11y-audit"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/figma-a11y-audit/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/figma-a11y-audit"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/figma-a11y-audit.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.00124 | $0.07447 |
| Opus 5.5 | $0.00050 | $0.02979 |
| Sonnet 5.5 | $0.00025 | $0.01489 |
| Haiku 4.5 | $0.00012 | $0.00745 |
Grade A, and why
figma-a11y-audit 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 1mo 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 — 616 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma A11y Audit — Erişilebilirlik Denetimi
Kullanım (v3.1+): SADECE
fmcp-ds-audit-orchestratoralt-skill'i olarak a11y deep-dive için çağrılır. Doğrudan entry point DEĞİL. Kullanıcı "a11y kontrol et" dediğinde önce orchestrator yüklenir.
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, Figma ekranını erişilebilirlik (a11y) standartlarına göre denetler. Platform-bazlı (iOS VoiceOver, Android TalkBack, Web ARIA) raporlar üretir. Topluluk "Uber a11y ekran okuyucu spesifikasyonları" örneğinden esinlenilmiştir.
Okuma + Yazma — Denetim sonuçlarını okur, isteğe bağlı olarak annotation frame ekler.
Prerequisites
- F-MCP Bridge plugin bağlı olmalı
- Hedef ekranın node ID'si veya URL'i bilinmeli
F-MCP skill koordinasyonu
- Önce (isteğe bağlı):
audit-figma-design-system(DS uyum denetimi) — a11y audit'ten bağımsız ama birlikte değerli - Sonra: Bulgular varsa
fix-figma-design-system-findingveyaapply-figma-design-systemile düzeltme; kod tarafındaimplement-designçıktısında a11y attribute'ları - İlişkili:
generate-figma-libraryFaz 4 (a11y denetimi) bu skill'i referans alır
WCAG 2.1/2.2 AA Hızlı Referans
Denetim sırasında bu 4 prensip ve 12 kriter referans alınmalıdır:
Algılanabilir (Perceivable)
- 1.1.1 Metin Dışı İçerik: Görseller, ikonlar ve dekoratif öğeler için alternatif metin veya
aria-hidden - 1.3.1 Bilgi ve İlişkiler: Başlık hiyerarşisi (H1→H2→H3), form etiketleri, tablo başlıkları programatik olarak belirlenmeli
- 1.4.3 Kontrast (Minimum): Normal metin ≥4.5:1, büyük metin (≥18px veya ≥14px bold) ≥3:1
- 1.4.11 Metin Dışı Kontrast: UI bileşenleri (buton kenarları, input border, ikon) ve grafik öğeleri ≥3:1 — sadece metin değil!
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.
- 1mo ago First seen · 616 lines · 124 tokens per session scan A 565f03e417e8
figma-a11y-audit is a skill published in the GitHub repository atezer/FMCP (10 stars, last pushed 10d ago), licensed MIT. It adds 124 tokens to every session and 7,447 once invoked, about $0.0005 per session on Opus 5.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
token-audit
Audit how design tokens are defined: tiers, naming, alias chains, raw values, orphans, DTCG readiness. Triggers: audit my tokens, token architecture review, token health check. Not for code consuming tokens (token-compliance), theme parity (theme-audit) or Figma variables (figma-variable-audit).
accessibility-per-component
Audit one design system component's accessibility against WCAG 2.2 AA: keyboard, screen reader, contrast, focus, ARIA, target size. Trigger: a11y audit, is this accessible, WCAG check, screen reader support, keyboard navigation check. Not for page- or product-wide audits.
component-decision-tree
Write "choosing between" pages (docs/choosing/) that route an intent to the right component via narrowing questions; YAML trees on request. Triggers: which component should I use, choose between X and Y, dialog vs drawer, selection guide. One chosen component: usage-guidelines.
figma-variable-audit
Audit Figma variable collections: tier mapping, naming, alias chains, modes, orphans; can fix in place with Figma Console MCP. Triggers: audit my Figma variables, review variable collections, Figma variable health. For token files in code use token-audit.
metadata-schema-generator
Generate per-component JSON metadata files (.ai/metadata/) from source: props, behaviour, composition, a11y contract, prohibited prop combinations. Triggers: component metadata schema, machine-readable component JSON, manifest for MCP/codegen. Prose for Figma: use ai-component-description.
theme-audit
Audit theme parity: tokens missing or unchanged per theme, component tokens bypassing semantics, contrast within each theme, resolver contexts, theme-switch regressions. Triggers: dark mode audit, theme coverage, brand variant parity. For general token structure use token-audit.