SEED is a design system that provides shared visual tokens, styling recipes, and UI components for React, iOS, Android, and Lynx, with Figma integration. It is used to build consistent products across platforms; the catalogue add-ons support agents working with its components, tools, documentation, and development workflows.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/daangn/seed-designnpx agentmods add skills/daangn/seed-design/seed-verify-figma-mcp-transportsWrote 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/daangn/seed-design/seed-verify-figma-mcp-transports)<a href="https://agentmods.dev/skills/daangn/seed-design/seed-verify-figma-mcp-transports"><img src="https://agentmods.dev/badge/skills/daangn/seed-design/seed-verify-figma-mcp-transports/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.
<a href="https://agentmods.dev/skills/daangn/seed-design/seed-verify-figma-mcp-transports"><img src="https://agentmods.dev/badge/skills/daangn/seed-design/seed-verify-figma-mcp-transports.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 8 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 47 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.1 | $0.00038 | $0.02018 |
| Opus 5 | $0.00019 | $0.01009 |
| Sonnet 5 | $0.00008 | $0.00404 |
| Haiku 4.5 | $0.00004 | $0.00202 |
Grade A, and why
seed-verify-figma-mcp-transports 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Figma MCP Transports
A Figma MCP tool answers the same question over two paths: REST (personal access token) and WebSocket (the Figma plugin). Fixing one and not the other still typechecks, so the drift is silent. Run both and compare mechanically.
두 경로의 구현 차이가 판단에 필요할 때만 packages/mcp/AGENTS.md를 읽는다.
[!IMPORTANT] Run this skill on the main thread. Phase 3 is a hard stop that waits on a person, and a subagent has nobody to ask — it will pass itself.
Prerequisites
FIGMA_PERSONAL_ACCESS_TOKENis set. If not, stop at Phase 0 and ask for it.- The Figma desktop app is installed.
- The tool under test is registered in
PROBESin the probe script. If it isn't, register it first — see the header comment in that file.
Phase 0: Decide what to inspect
Both transports need a target, so this comes before any probing — REST in Phase 1 already needs it.
검증 기준은 변경 diff에서 스스로 도출한다. 사용자가 이미 조건을 만족하는 layer URL을 제공했으면 그대로 사용한다. 그렇지 않으면 특정 node가 아니라 필요한 layer 형태를 설명해 URL을 요청한다. "A frame containing a layer with two or more annotations, and a text layer with none"은 답할 수 있지만, "Give me a layer URL"은 검증 설계를 사용자에게 넘긴다.
Start from this checklist and cut what your change doesn't touch:
| Cover | Why |
|---|---|
| The queried node itself carrying a value | Catches a traversal that skips its own root |
| A descendant carrying a value | The recursive collection path |
A leaf (no children) |
Whether a non-container node throws |
A page (CANVAS / PAGE) |
The plugin-only loadAsync path, plus the type-vocabulary difference |
| A node inside a component instance | IDs composed as I<a>;<b>;<c> |
The last two apply to every tool. The rest apply only when the tool walks a tree.
Ask with AskUserQuestion, and ask for a layer URL — parseFigmaUrl takes the file key and node id straight out of it, so nobody has to read ids off a canvas.
If the same file gets reused across runs, put its key in SEED_MCP_PROBE_FILE_KEY and pass only --node-id afterwards.
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 Changed · -2 lines · -88 tokens per session 35d1a25cd593
- 8d ago First seen · 165 lines · 126 tokens per session scan A bfb9c5d51f20
seed-verify-figma-mcp-transports is a skill published in the GitHub repository daangn/seed-design (1,119 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 2,018 once invoked, about $0.0002 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-04.
Other skills, from other repositories
design-qa-checklist
Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use handoff-spec.
accessibility-per-component
Run an accessibility audit on a specific design system component. Trigger when someone says: accessibility check, a11y audit, WCAG compliance, is this accessible, check accessibility, does this meet WCAG, screen reader support, keyboard navigation check, or anything about auditing the accessibility of a specific…
schema-validator
Validate token files against DTCG 2025.10, Style Dictionary, or custom schemas. Trigger when someone says: validate token JSON, check my token files for errors, schema validation for tokens, are my token files valid, DTCG compliance check, validate token format, or anything about checking whether token files are…
design-qa
A visual checking and correction workflow that compares a running app screen with its Figma source using captures, overlays, difference maps, and pixel measurements. An overlay places two images together so mismatches are easier to see.
fmcp-ds-audit-orchestrator
Figma ekranlarını 5 kategori açısından platform-agnostic denetler (DS compliance / a11y / drift / visual QA / impact). Read-only çalışır; bulguları raporlar, düzeltmeleri sadece önerir — mutation için onay + ayrı agent. Her platformda çalışır. Condensed-first: Essentials bölümü %80 case'i kapsar, Advanced sadece edge…
design-fidelity-verify
Prove a running app matches its design spec by measuring rendered values, not eyeballing a screenshot. Use when the user says "verify the design", "is this pixel-perfect", "check against Figma", "does the app match the design", or "design QA this screen". Runs a bounded vision+numeric loop over web or mobile…