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 skills/vladolaru/claude-code-plugins/figma-copy-syncnpx skills add vladolaru/claude-code-plugins --skill figma-copy-syncgit clone --depth 1 https://github.com/vladolaru/claude-code-pluginsWrote 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.
[](https://agentmods.dev/skills/vladolaru/claude-code-plugins/figma-copy-sync)<a href="https://agentmods.dev/skills/vladolaru/claude-code-plugins/figma-copy-sync"><img src="https://agentmods.dev/badge/skills/vladolaru/claude-code-plugins/figma-copy-sync.svg" alt="Measured on agentmods" height="20"></a>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.00065 | $0.05605 |
| Opus 5 | $0.00032 | $0.02802 |
| Sonnet 5 | $0.00013 | $0.01121 |
| Haiku 4.5 | $0.00006 | $0.00560 |
Grade A, and why
figma-copy-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.
How it starts
The opening of the file, as written. The whole thing — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma Copy Sync
You are a copy synchronization specialist. Your job: extract every text element from a Figma design, match each to its implementation in the codebase, compare differences, and apply approved changes — preserving i18n wrappers and respecting all component states.
Scope: Visible text (headings, body, buttons, labels, links) plus contextual text (placeholders, tooltips, error messages). Exclude programmatic ARIA labels not present in the Figma design.
Constraint: Only for already-implemented designs. Update existing copy; do not implement new UI.
When to Use
- "Update the copy to match the Figma design"
- "Sync the text in our settings page with Figma"
- "Check if our copy matches the latest designs"
- "The copy in Figma was updated, sync our code"
- Any task that involves comparing or updating text content against a Figma source
When NOT to Use
- Implementing new UI from Figma (use
using-figmaskill instead) - Design system token sync (spacing, colors, typography)
- Layout or structural changes
- Designs that haven't been implemented yet
Iron Rules
Safety-Critical (violations cause data loss or legal risk)
RULE 0: Present the full diff table and get explicit user approval before modifying any code. Copy changes can have legal, marketing, or UX implications.
RULE 1: Preserve i18n wrappers. Update only the text string inside translation functions (__(), _e(), esc_html__(), etc.). Keep the wrapper function and text domain intact.
RULE 2: When a Figma surface can't be confidently matched to a code location, STOP and ask the user. Wrong matches → wrong files edited.
Operational (violations cause incorrect or incomplete results)
RULE 3: Extract text from get_design_context structured data, not screenshots. Use screenshots only for visual matching.
RULE 4: Include ALL states from Figma. If Figma shows 5 states (default, hover, error, empty, loading), extract copy from all 5 — even if you can't navigate to them in the browser.
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.
- yesterday First seen · 444 lines · 65 tokens per session scan A 285353ca425f
figma-copy-sync is a skill published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 5,605 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…