What is storysync-diff?

A command that compares a Figma design file with the project's design tokens and Storybook components. Figma is a design tool, while Storybook is a tool for viewing and testing interface components in code.

Use it to compare colors, spacing, corner shapes, component variants, and other design details between Figma and the codebase.

It finds differences between what was designed and what was implemented before those differences become harder to fix.

storysync-diff — Command for coding agents by brendanciccone: A command that compares a Figma design file with…

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/brendanciccone/storysync/storysync-diff

Clone the repo

git clone --depth 1 https://github.com/brendanciccone/storysync

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/brendanciccone/storysync/storysync-diff.svg)](https://agentmods.dev/commands/brendanciccone/storysync/storysync-diff)

Your own site

<a href="https://agentmods.dev/commands/brendanciccone/storysync/storysync-diff"><img src="https://agentmods.dev/badge/commands/brendanciccone/storysync/storysync-diff.svg" alt="Measured on agentmods" height="20"></a>

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 448 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.

Model	Per session	Once invoked
Fable 5	$0.00012	$0.00448
Opus 5	$0.00006	$0.00224
Sonnet 5	$0.00002	$0.00090
Haiku 4.5	$0.00001	$0.00045

Measured 4d ago against content hash 072cbde49679, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

storysync-diff 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 4d 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/storysync-diff.md · 27 lines

What it actually says

Compare the current Figma file against this codebase's design tokens and Storybook components, then report drift in either direction. Use the storysync skill at .claude/skills/storysync.md (Audit section).

Figma file key: $ARGUMENTS

If the user did not provide a file key (or $ARGUMENTS is empty), ask for it. The file key is the part of a Figma URL between /design/ and the next /.

Workflow:

Read Figma variables — call use_figma to enumerate every variable collection and its resolved values (use figma.variables.getLocalVariableCollectionsAsync() and convert COLOR values to hex).
Read Figma components — call use_figma to enumerate every component set and its variant properties (use figma.root.findAllWithCriteria({ types: ['COMPONENT_SET'] }) and read componentPropertyDefinitions).
Run storysync tokens --json --project . for code-side tokens.
Run storysync map --storybook http://localhost:6006 --json for code-side components.
Compare tokens by name within each category. Normalize before comparing: lowercase hex, convert rem→px, strip units. Match Figma collection names to code categories (Colors→colors, Border Radius→radius, etc.).
Compare components by name (case-insensitive). For each: missing props, extra props, missing/extra values per prop.
Report drift grouped by category/component:
- + missing from Figma (in code, not in Figma)
- - missing from code (in Figma, not in code)
- ~ value mismatch (both exist, values differ)
End with a summary: N tokens matched / mismatched / missing. N components matched / mismatched. If everything matches, confirm "Figma and code are in sync."

Refer to .claude/skills/storysync.md Audit section for the full procedure and edge cases.

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.

4d ago First seen · 27 lines · 12 tokens per session scan A 072cbde49679

Subscribe to this mod's changes

storysync-diff is a command published in the GitHub repository brendanciccone/storysync (66 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 448 once invoked, about $0.0001 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-30.

Design and UX

storysync-diff

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

ui-flow-review

template-ui

responsive-design-specialist

study

4-generate

audit-ux