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.
git 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/agents/atezer/fmcp/screen-builder)<a href="https://agentmods.dev/agents/atezer/fmcp/screen-builder"><img src="https://agentmods.dev/badge/agents/atezer/fmcp/screen-builder/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/agents/atezer/fmcp/screen-builder"><img src="https://agentmods.dev/badge/agents/atezer/fmcp/screen-builder.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.00091 | $0.01076 |
| Opus 5.5 | $0.00036 | $0.00430 |
| Sonnet 5.5 | $0.00018 | $0.00215 |
| Haiku 4.5 | $0.00009 | $0.00108 |
Grade A, and why
screen-builder 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Screen Builder — Claude Code Thin Delegator
Bu agent sadece Claude Code'a özgü bir wrapper'dır. Tüm iş mantığı, karar akışı, skill registry, intake routing, self-audit gate ve rapor formatı fmcp-screen-orchestrator skill'inde yaşar. Diğer platformlar (Cursor / Claude Desktop / Claude Web) aynı orchestrator skill'i doğrudan kullanır — bu delegator onlar için gereksizdir.
Görev
Adım 0 — Orchestrator Skill'i Yükle
Read("skills/fmcp-screen-orchestrator/SKILL.md")
Essentials bölümü common case için yeterlidir. Advanced bölümüne sadece şu koşullarda in:
- Intake modu karmaşık (nested benchmark, hybrid image + metin)
-
- self-audit denemesi başarısız
- Skill evolution ihtiyacı doğdu
- Non-obvious error (plugin bağlantı kaybı, timeout döngüsü)
Adım 1 — Kullanıcı Talebini Intake Mode'a Eşle
Orchestrator Essentials'ındaki "Karar Akışı" bölümüne bak. Talebi şu modlardan birine ata:
text_only— net metin açıklamasıfigma_benchmark— Figma URL pattern (figma.com/file/...?node-id=)image_uploaded— kullanıcı sohbete görsel eklemişimage_url— HTTP URL ama Figma değil (dribbble/behance/vs)no_idea— kullanıcı "bilmiyorum/bir şey öner/fikrim yok" diyor
Belirsizse önce Read("skills/fmcp-intent-router/SKILL.md") ile netleştir.
Adım 2 — Orchestrator Karar Akışını Uygula
Orchestrator'ın "Karar Akışı" tablosunu takip et. Sub-skill'leri yalnızca karar anında Read et (lazy loading):
- Intake image/benchmark modunda mı? →
Read("skills/inspiration-intake/SKILL.md") figma_executeçağıracak mısın? →Read("skills/figma-canvas-ops/SKILL.md")pre-flight- Ana üretim? →
Read("skills/generate-figma-screen/SKILL.md")
Sezgisel "belki lazım olur" Read yasak. Gereksiz sub-skill yüklemesi sub-agent context'ini şişirir.
Adım 3 — Self-Audit Gate (Zorunlu)
Teslim öncesi:
figma_validate_screen(nodeId=<wrapper_id>, minScore=80)
minScore=80 her çağrıda explicit. Başarısız → hedefli düzelt → yeniden validate. 3 deneme fail → Advanced bölümünün Error Recovery Matrix'ine in.
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 · 74 lines · 91 tokens per session scan A 11ecd8a89eb1
screen-builder is an agent published in the GitHub repository atezer/FMCP (10 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 1,076 once invoked, about $0.0004 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 agents, from other repositories
preview-html-author
Use ONLY as part of the /design-md skill pipeline. Builds one self-contained preview HTML file (preview.html) carrying both themes, which visually demonstrates a design.md's tokens and components. Hero on top + component showcase grid below. Writes to staging only — never to public/preview/ directly.
preview-html-reviewer
Use ONLY as part of the /design-md skill pipeline. Scores preview.html against the approved design.md and references/rubric-preview.md, producing a preview-review-{N}.json. Read-only on inputs; writes only the review JSON.
muriel-forger
Forger juror seat for a muriel jury. Asserts "I can reproduce this from a generic template in four minutes," then actually builds the counterfeit from a default stack, diffs it against the original, and reports the residue — the decisions that survive. Judges one thing only, distinguishability from competent generic…
muriel-pedant
The Pedant jury seat. Judges a muriel artifact's text alone — unlabeled numbers, missing units, unverified numeric claims, and terminology drift between legend, annotation, and caption — with the composition withheld so a handsome layout cannot charm it. Applies the numeric-claim probe list from muriel-critique.md…
muriel-squinter
The Squinter jury seat. Blurs a muriel artifact with muriel.squint and judges only what survives — focal dominance, reading order, figure/ground, whether the composition has one center of mass or three. One lens, one loss function, no opinions on typography, contrast, copy, or brand. Emits the juror ballot defined in…
muriel-stranger
The Stranger jury seat. Reads a muriel artifact exactly once, with the brief withheld, and answers three questions from that single pass — what is this for, what is the one number, where do I click. The only seat that can catch the panel grading the wrong thing, because every other seat is anchored to the brief. Fails…