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-token-sync-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-token-sync-orchestrator)<a href="https://agentmods.dev/skills/atezer/fmcp/fmcp-token-sync-orchestrator"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/fmcp-token-sync-orchestrator.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.00079 | $0.02352 |
| Opus 5 | $0.00039 | $0.01176 |
| Sonnet 5 | $0.00016 | $0.00470 |
| Haiku 4.5 | $0.00008 | $0.00235 |
Grade A, and why
fmcp-token-sync-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 8d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FMCP Token Sync Orchestrator
Essentials (Üst Bölüm — %80 Case İçin Yeterli)
Ortak Protokol (Condensed — full: agents/_orchestrator-protocol.md)
- Skill Registry açık — tahmin yasak
- Intent Routing — platform belirsiz → kullanıcıya sor (AskUserQuestion / düz metin)
- Cheap-First —
figma_get_variables(verbosity="summary")yeterli, full sadece eksik binding keşfinde - Cache-First — tokens için cache yok (hızlı değişir), opsiyonel
.claude/token-sync-log.md - User Onay — diff preview olmadan WRITE YOK (mutlak kural)
- Self-Audit — write sonrası binding coverage raporu (hardcoded kalan node sayısı)
- Skill Evolution — yeni platform için iki aşamalı onay
- Türkçe rapor — metrik bloğu sonunda
Skill Registry (Ref Only)
| Skill | Dosya yolu | Trigger | Common case lazım mı? |
|---|---|---|---|
design-token-pipeline |
skills/design-token-pipeline/SKILL.md |
Token export/import | HER ZAMAN (ana motor) |
code-design-mapper |
skills/code-design-mapper/SKILL.md |
Component ↔ Figma mapping | Sadece component mapping istenirse |
design-system-rules |
skills/design-system-rules/SKILL.md |
Platform-specific rule generation | Sadece rule generation istenirse |
Platform Routing
| Sinyal | Platform | Standard hedef path |
|---|---|---|
.css, :root, var(--...), tokens.css |
CSS | src/styles/tokens.css |
tailwind.config.*, theme.extend |
Tailwind | tailwind.config.js → theme.extend |
.swift, UIKit, SwiftUI, Color(...) |
Swift | Sources/DesignTokens/Tokens.swift |
.kt, Compose, @Composable, MaterialTheme |
Compose | app/src/main/java/.../DesignTokens.kt |
.scss, $token-... |
Sass | src/styles/_tokens.scss |
| Hiçbiri net değil | — | AskUserQuestion (4 platform seçeneği) |
Diff Preview Before Write (Zorunlu Akış)
- Dry-run:
Read("skills/design-token-pipeline/SKILL.md")+ workflow'u çalıştır ama dosyaya yazma → çıktıyı buffer'a al - Mevcut dosya varsa: mevcut içerikle yeni içerik arası unified diff üret
- Diff'i sohbete yaz:
--- current tokens.css +++ new tokens.css @@ -12,3 +12,5 @@ --color-primary: #0066cc; - --color-secondary: #666; + --color-secondary: #4a4a4a; + --color-success: #10b981; - Onay al: AskUserQuestion / düz metin: "Bu değişiklikleri uygulayayım mı? (Evet / Hayır / Sadece bazıları)"
- Onay sonrası
WriteveyaEditile dosyaya yaz - Mevcut dosya yoksa: sadece yeni içeriği göster, onay al, sonra
Write
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.
- 8d ago First seen · 199 lines · 0 tokens per session scan A 859dd8272201
fmcp-token-sync-orchestrator is a skill published in the GitHub repository atezer/FMCP (9 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 2,352 once invoked, about $0.0004 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
design-to-code-check
Check alignment between a specific design specification and its code implementation — a focused, single-component or single-screen comparison. Trigger when someone says: does this match the design, check implementation, design code alignment, what's different between the design and the build, spec check…
design-engineering
Premium design engineering skill for agentic workflows — produces high-end, distinctive UI designs using DESIGN.md as the portable contract across Pencil MCP (in-IDE canvas), Figma MCP (team handoff + design tokens), and Google Stitch (vibe exploration + AI generation). Enforces anti-generic principles, WCAG 2.2 AA…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
refero-design
Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive design, typography, color, spacing, motion, icons, accessibility, copywriting, conversion, and anti-AI-slop work. Use this…
figma-design-handoff
Figma-to-code design handoff patterns including Figma Variables to design tokens pipeline, component spec extraction, Dev Mode inspection, Auto Layout to CSS Flexbox/Grid mapping, and visual regression with Applitools. Use when converting Figma designs to code, documenting component specs, setting up design-dev…
s2-docs
Look up Spectrum 2 (S2) component documentation, design guidelines, and usage patterns when building with React Spectrum or Spectrum Web Components. Use when the user mentions Spectrum, S2, React Spectrum, RSP, Spectrum Web Components, or SWC, or names a Spectrum component (Button, Picker, ComboBox, TextField…