agentmods.dev

storysync-push

storysync-push is a command for Claude Code from brendanciccone/storysync. It costs 12 tokens per session (547 once invoked), scanned A, original, MIT.

A command that sends Storybook components and design tokens from a code project into Figma, a collaborative interface-design tool. It reads component styles and maps variants so the Figma file can reflect the coded components.

In plain words
What is it for?
Use it to sync design-token collections, map Storybook variants, and create or update Figma representations of coded components.
Why use it?
It reduces the manual work of copying colors, spacing, typography, and component variations from code into a design file. It also provides checks for missing tokens or an unavailable Storybook server.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths.

not rated 66repo 7d ago A scan 12 tokens original MIT

Good fit Use it to sync design-token collections, map Storybook variants, and create or update Figma representations of coded components.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/brendanciccone/storysync/storysync-push
View source ↗ brendanciccone/storysync
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/brendanciccone/storysync

Made for: Claude Code.

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 storysync-push

README.md
[![agentmods](https://agentmods.dev/badge/commands/brendanciccone/storysync/storysync-push.svg)](https://agentmods.dev/commands/brendanciccone/storysync/storysync-push)
Your own site
<a href="https://agentmods.dev/commands/brendanciccone/storysync/storysync-push"><img src="https://agentmods.dev/badge/commands/brendanciccone/storysync/storysync-push.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 547 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.00012 $0.00547
Opus 5 $0.00006 $0.00273
Sonnet 5 $0.00002 $0.00109
Haiku 4.5 $0.00001 $0.00055

Measured 8d ago against content hash d8baab36f83c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

storysync-push 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.

commands/storysync-push.md · 24 lines

What it actually says

Push design tokens and Storybook components from this codebase into Figma using the storysync skill at .claude/skills/storysync.md.

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:

  1. Run storysync tokens --json --project . to extract design tokens from the project. If no tokens are found, skip token sync and continue with components.
  2. For each token category, call use_figma to create or update a matching Figma variable collection. Convert rem values to px (1rem = 16px). Use COLOR for colors and FLOAT for numeric tokens.
  3. Run storysync map --storybook http://localhost:6006 --json to get component variant mappings. If Storybook isn't running on port 6006, ask the user for the correct URL.
  4. REQUIRED — Read each component's source file (.tsx/.jsx) and any imported style files. Build a styling spec per variant value with: background fill (hex), text color (hex), border, border radius (px), padding (px), font size (px) + weight, shadow, and auto-layout direction. Source patterns: Tailwind classes, cva/clsx/cn calls, CSS modules, styled-components, inline styles, theme tokens. Do not skip — a use_figma call without these values produces a broken library.
  5. Group components by their category field. Create one Figma page per top-level category (Forms, Data Display, etc.). Place each component set on the matching page.
  6. Call use_figma per component. The instruction MUST embed the styling spec from step 4 — every variant value needs concrete fill, text color, padding, radius, border, font size, and shadow. Bind fills/spacing/radius/typography/shadows to the variable collections from step 2 where possible.
  7. Verify each component looks correct; fix any styling issues with a follow-up use_figma call.
  8. Summarize what was synced: token collections (count per category), components grouped by page, variant counts, any failures or caps.

Refer to .claude/skills/storysync.md for the full procedure including edge cases and visual accuracy guidelines.

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. 8d ago First seen · 24 lines · 12 tokens per session scan A d8baab36f83c

Subscribe to this mod's changes

storysync-push is a command published in the GitHub repository brendanciccone/storysync (66 stars, last pushed 7d ago), licensed MIT. It adds 12 tokens to every session and 547 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
Related

Other commands, from other repositories

profile

Save, load, inspect, update, reset, or delete diagram-design client profiles.

cathrynlavery/diagram-design · 16 tokens

ui-flow-review

Review menus, HUD, navigation, and player flow from a UX perspective.

MRCalderon3D/everything-game-dev-code · 15 tokens

responsive-design-specialist

Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.

imsaif/design-with-claude · 36 tokens

ppt-image2-editable-rebuild

Rebuild image2 or imagegen reference slides as editable PowerPoint decks.

wwe-dog/ppt-image2-editable-rebuild · 15 tokens

team-ui

Orchestrate UI/UX design team.

striderZA/OpenCodeGameStudios · 11 tokens

p3-ux-wireframes

Creates wireframes (ASCII art) for the most important screens with interaction descriptions.

jonase47/ccpr · 0 tokens