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 fmcp-screen-orchestratorgit 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/fmcp-screen-orchestrator)<a href="https://agentmods.dev/skills/atezer/fmcp/fmcp-screen-orchestrator"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/fmcp-screen-orchestrator/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/fmcp-screen-orchestrator"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/fmcp-screen-orchestrator.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.00040 | $0.06867 |
| Opus 5 | $0.00020 | $0.03433 |
| Sonnet 5 | $0.00008 | $0.01373 |
| Haiku 4.5 | $0.00004 | $0.00687 |
Grade A, and why
fmcp-screen-orchestrator 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 9d 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 — 452 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FMCP Screen Orchestrator
Essentials
Ortak Protokol
- Skill Registry açık — tahmin yasak, sezgisel Read() yasak
- Intent Routing — belirsiz → Read fmcp-intent-router
- Cheap-First —
depth=1,verbosity="summary", screenshot sadece onay kapısında, ≤5 execute - Cache-First —
.claude/design-systems/<lib>/cache'i API'den ÖNCE oku - Onay Kapıları — approach / destructive / evolution / 3. audit fail
- Self-Audit —
figma_validate_screen(nodeId, minScore=80)ZORUNLU - Skill Evolution — iki aşamalı onay +
# DRAFT — PENDING APPROVALbanner - Türkçe Raporlama — metrik bloğu zorunlu
Skill Registry
| Skill | Trigger | Common case? |
|---|---|---|
fmcp-intent-router |
Belirsiz intent | Sadece belirsizlikte |
inspiration-intake |
image/figma_benchmark | Sadece bu modlarda |
generate-figma-screen |
Net screen creation | HER ZAMAN (ana motor) |
figma-canvas-ops |
Her figma_execute öncesi | HER ZAMAN (pre-flight) |
fmcp-screen-recipes |
Fast Path match | Sadece Fast Path'te |
apply-figma-design-system |
Mevcut ekranı DS'ye hizala | Sadece remediation |
DS Library Registry (v3.3+ — Agent Just Knows)
Registry'nin iki kaynağı var; okuma sırası:
.claude/design-systems/registry.local.md(kullanıcıya özel, gitignore'lu) — Adım -2 oto-uyumlanma veya/ds-addtarafından otomatik yazılır. VARSA tek doğru kaynak budur.- Aşağıdaki şablon tablo (repo'da paylaşılan takım varsayılanları — placeholder ise yok say).
| Library Name | libraryFileKey | Açıklama |
|---|---|---|
| ❖ Ana-DS (örnek) | <ANA_DS_FILE_KEY> |
Ana DS (web + mobile ortak bileşenler, tokenlar) |
| ❖ Ana-DS Mobil (örnek) | <MOBIL_DS_FILE_KEY> |
Mobile-only bileşenler (navbar, bottomsheet, input...) |
| 🙂 Icons (örnek) | <ICONS_FILE_KEY> |
Icon component library |
| 💼 Assets (örnek) | <ASSETS_FILE_KEY> |
Illüstrasyon / asset kütüphanesi |
Kullanıcı registry'deki bir DS ile "X yap" dediğinde agent otomatik ilgili library'leri enumerate eder. Registry doluysa URL/file key SORMAZ.
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.
- 9d ago First seen · 452 lines · 40 tokens per session scan A 4b4edc91e13a
fmcp-screen-orchestrator is a skill published in the GitHub repository atezer/FMCP (9 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 6,867 once invoked, about $0.0002 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…