ds-sync

A command for synchronizing an existing design-system library with Figma. It can synchronize everything, selected sections, or continue an interrupted synchronization.

In plain words
What is it for?
Updating a library's tokens, components, icons, mobile designs, or assets from Figma, either fully, partially, from a saved checkpoint, or from the beginning.
Why use it?
It avoids repeating completed work when a synchronization stops partway through and lets you update only the section you need.

Command

Install

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.

agentmods
npx agentmods add commands/atezer/fmcp/ds-sync
Clone the repo
git clone --depth 1 https://github.com/atezer/FMCP
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,761 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02761
Opus 5 $0.00000 $0.01380
Sonnet 5 $0.00000 $0.00552
Haiku 4.5 $0.00000 $0.00276

Measured yesterday against content hash 58719dc2e013, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ds-sync 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 yesterday.

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.

commands/ds-sync.md · 315 lines

How it starts

The opening of the file, as written. The whole thing — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design System Güncelle (Resume Destekli)

Mevcut bir tasarım sistemi kütüphanesini Figma'dan senkronize eder. Tam sync, kısmi sync ve resume (yarım kalanı devam ettirme) destekler.

Argüman

$ARGUMENTS

Argüman olabilir:

  • Boş → aktif veya tek kütüphaneyi sync et (belirsizse kullanıcıya sor)
  • <library-id> → o kütüphanenin tüm section'larını sync et
  • <library-id> <section> → sadece o section (tokens, components, icons, mobile, assets)
  • <library-id> --restart → checkpoint'ten bağımsız sıfırdan başla

Adım 1: Hedef Belirleme

  1. $ARGUMENTS boşsa:

    • .claude/design-systems/ altındaki kütüphaneleri listele
    • Tek kütüphane → onu kullan
    • Birden fazla → kullanıcıya sor: "Hangi kütüphaneyi güncelleyeyim?"
  2. Kütüphane ID → .claude/design-systems/<id>/ dizini yoksa:

    ❌ "<id>" adında bir kütüphane bulunamadı.
    💡 Mevcut kütüphaneleri görmek için: ls .claude/design-systems/
    
  3. Section belirtilmemişse → tüm section'lar (meta'ya göre)


Adım 2: _meta.md Oku

.claude/design-systems/<id>/_meta.md dosyasını oku ve şu bilgileri çıkar:

  • Kaynak-section eşleştirme tablosu
  • Sync durumu (TAMAMLANDI / YARIM KALDI / HATA)
  • Son sync tarihi
  • İstatistikler

Eğer durum "YARIM KALDI" ise:

📋 Son sync yarım kalmış: components 87/163
Kaldığı yerden devam edeyim mi? (evet / sıfırdan başla / iptal)

Adım 3: Bağlantı Kontrolü

mcp__figma-mcp-bridge__figma_list_connected_files çağır.

Kaynak-section tablosundaki her file key için:

  • Bağlı → ✅ işaretle
  • Bağlı değil → ❌ işaretle

Hiçbir kaynak bağlı değilse → DUR:

❌ Hiçbir Figma kaynağı bağlı değil.
Lütfen:
1. İlgili Figma dosyalarını aç
2. F-MCP Bridge plugin'i çalıştır
3. Tekrar dene

Bazı kaynaklar bağlı, bazıları değil → kullanıcıya bildir:

⚠️ Bazı kaynaklar bağlı değil:
✅ main (❖ Ana-DS)
❌ assets (💼 Assets)

Sadece bağlı olanları güncelleyeyim mi? (evet / iptal)

Adım 4: Yedekleme

Her section'ın mevcut MD dosyasını .bak olarak kopyala:

Read the full file on GitHub · 315 lines

Changes

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.

  1. yesterday First seen · 315 lines · 0 tokens per session scan A 58719dc2e013

Subscribe to this mod's changes

ds-sync is a command published in the GitHub repository atezer/FMCP (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,761 tokens. 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.