track-ds-changes

track-ds-changes is a command for Claude Code from atezer/FMCP. It costs 25 tokens per session (247 once invoked), scanned A, original, MIT.

A command for tracking changes in Figma design-system files, which are shared collections of interface components, styles, icons, and design values. It checks file snapshots and can prepare a work outline for developers when changes are found.

In plain words
What is it for?
Use it with Figma file links to compare design-system changes, review component or token updates, and draft follow-up development work.
Why use it?
It turns design-file changes into an old-to-new summary without opening a development task automatically. It also makes clear when a required Figma connection is missing.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the figma-mcp-bridge plugin — 29 skills, 10 commands, 3 agents, 1 MCP server shipped together

Good fit Use it with Figma file links to compare design-system changes, review component or token updates, and draft follow-up development work.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/atezer/fmcp/track-ds-changes
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.

Clone the repo
git clone --depth 1 https://github.com/atezer/FMCP

Made for: Claude Code.

Or install figma-mcp-bridge, the plugin that ships this one along with the rest of its 29 skills, 10 commands, 3 agents, 1 MCP server.

Wrote 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.

agentmods badge for track-ds-changes

README.md
[![agentmods](https://agentmods.dev/badge/commands/atezer/fmcp/track-ds-changes/github.svg)](https://agentmods.dev/commands/atezer/fmcp/track-ds-changes)
Your own site
<a href="https://agentmods.dev/commands/atezer/fmcp/track-ds-changes"><img src="https://agentmods.dev/badge/commands/atezer/fmcp/track-ds-changes/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.

agentmods 80×15 button for track-ds-changes

Your own site · 80×15
<a href="https://agentmods.dev/commands/atezer/fmcp/track-ds-changes"><img src="https://agentmods.dev/badge/commands/atezer/fmcp/track-ds-changes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 247 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00025 $0.00247
Opus 5.5 $0.00010 $0.00099
Sonnet 5.5 $0.00005 $0.00049
Haiku 4.5 $0.00003 $0.00025

Measured 13d ago against content hash 366eb1b3c4e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

track-ds-changes 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 13d 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.

commands/track-ds-changes.md · 17 lines

What it actually says

DS Değişiklik Takibi

ds-change-tracker skill'ini uygula (skills/ds-change-tracker/SKILL.md).

Girdi: $ARGUMENTS (Figma dosya URL'leri; fileKey'leri URL'den çıkar).

  1. figma_get_status ile bağlantıyı doğrula; bağlı değilse kullanıcıdan plugin'i açmasını iste.
  2. Dosya için önceki snapshot varsa snapshot karşılaştırması yap; yoksa baz snapshot al.
  3. Kullanıcı geçmişteki bir anı soruyorsa ve REST token varsa sürüm geçmişiyle bileşen/yapı farkını çıkar (token değer farkı bu yolla alınamaz — bunu belirt).
  4. Raporu "eski → yeni" biçiminde sun.
  5. Değişiklik varsa iş taslağı öner; onay almadan iş açma.
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. 13d ago First seen · 17 lines · 25 tokens per session scan A 366eb1b3c4e9

Subscribe to this mod's changes

track-ds-changes is a command published in the GitHub repository atezer/FMCP (10 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 247 once invoked, about $0.0001 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-10-07.