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 agentmods add rules/brendanciccone/storysync/cursorgit clone --depth 1 https://github.com/brendanciccone/storysyncWhat 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.00011 | $0.02130 |
| Opus 5 | $0.00005 | $0.01065 |
| Sonnet 5 | $0.00002 | $0.00426 |
| Haiku 4.5 | $0.00001 | $0.00213 |
Grade A, and why
cursor 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 2d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
storysync — Storybook to Figma
Read components from Storybook MCP and recreate them in Figma MCP as a visually accurate component library, with design token foundations.
Requirements
- Storybook dev server running with
@storybook/addon-mcp(Vite-based Storybook 10.1+, Node 18+) - Storybook MCP connected (endpoint at
/mcpon the dev server) - Figma MCP connected (
/add-plugin figmaor addhttps://mcp.figma.com/mcp) - Figma Full seat (Dev seats are read-only)
- storysync installed:
npm install -g storysyncornpx storysync
Tokens
Before syncing components, extract design tokens from the project and create Figma variable collections. This ensures components can bind to variables instead of hardcoded values.
- Extract tokens — run storysync to detect and extract tokens from the project:
npx storysync tokens --json --project .
This auto-detects the token source (Tailwind config, CSS custom properties, or theme files) and outputs structured JSON with collections of tokens by category (colors, spacing, typography, radius, shadows). If it returns no collections, skip to Components.
-
Preview tokens — optionally, run
npx storysync tokens --project .(without--json) for a human-readable preview. -
Create Figma variable collections — use the JSON output to create Figma variables via
use_figma, one collection at a time. Convert rem values to px (1rem = 16px) for Figma FLOAT variables. Use FigmaCOLORtype for colors andFLOATtype for spacing, radius, and font sizes. -
Verify — confirm the variable collections were created with the expected count. If any are missing, retry.
Components
- List and map components — run storysync to read Storybook components and compute variant mappings:
npx storysync map --storybook http://localhost:6006 --json
This outputs structured JSON with each component's variant properties (name, type, values, default), combination count, and a title/category reflecting the component's place in Storybook's sidebar (e.g. title: "Forms/Button", category: "Forms"). Use the category to organize the Figma file — see "Organization" below.
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.
- 2d ago First seen · 135 lines · 11 tokens per session scan A e87b332d9ccb
cursor is a cursor rule published in the GitHub repository brendanciccone/storysync (66 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 2,130 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.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.