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
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 skills add daangn/seed-design --skill seed-verify-lynx-componentgit clone --depth 1 https://github.com/daangn/seed-designWrote 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-lynx-component)<a href="https://agentmods.dev/skills/daangn/seed-design/seed-verify-lynx-component"><img src="https://agentmods.dev/badge/skills/daangn/seed-design/seed-verify-lynx-component/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-lynx-component"><img src="https://agentmods.dev/badge/skills/daangn/seed-design/seed-verify-lynx-component.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
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 →
- medium MCP Rug Pull · line 17 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 99 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 100 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.03175 |
| Opus 5.5 | $0.00015 | $0.01270 |
| Sonnet 5.5 | $0.00008 | $0.00635 |
| Haiku 4.5 | $0.00004 | $0.00317 |
Grade A, and why
seed-verify-lynx-component 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 24d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lynx 컴포넌트 검증
현재 worktree의 한 Lynx 컴포넌트와 관련 문서·실행 예제를 검증한다. 결과는 어떤 환경에서 무엇을 직접 확인했는지와 미확인 범위를 분리한 기록이다. seed-orchestrate-component를 통한 협업에서는 구현자와 독립된 검증 담당이 기본 장면과 최종 결과를 확인한다. 구현자의 요약·API 리뷰·작업 종료는 승인 근거가 아니다.
GPT-6-Astra와 GPT-5.6 Luna·Terra·Sol에 같은 필수 검사·수락 기준·증거·권한 경계를 적용한다. 모델별 보조 지침이 필요하면 실행 환경에서 실제 모델과 지침 묶음을 명시적으로 연결하고 로딩을 확인한다. 모델의 자기 식별이나 모델 전환만으로 지침이 바뀐다고 가정하지 않는다.
범위와 경계
- 한 번에 한 컴포넌트와 요청된 시나리오·변경 표면을 대상으로 한다. 새 컴포넌트나 전체 동등성 주장은 모든 관련 시나리오를 포함한다.
- 대상 경로의 package 공개 export·Recipe·문서 예제·
examples/lynx-spa소비 경로·필요한 생성물만 읽기 전용으로 확인한다. 원천 파일의 존재만으로 통과시키지 않는다. - React와 Lynx가 같은 사용자 결과를 주장하는 시나리오는 내용 단위로 비교한다. 브라우저, native bundle, 로컬 Lynx 런타임, 실제 기기의 결과를 서로 합치지 않는다.
- 검증자는 컴포넌트·문서 소스를 수정하지 않는다. 승인된 검증에 필요한 기존 빌드의 산출물 생성과 소유 session의 상태 변경은 허용하되 저장소의 수정 금지 경로·생성 절차·소유권 규칙을 따른다. 문제가 발견되면 원인과 수정 범위를 보고한다.
- 협업에서는 통합 담당이 넘긴 변경본 식별 정보와 bundle을 확인한다. 후속 수정이 있으면 영향받은 항목을
미확인으로 되돌린다. 검증 분담과 자원에 따라 공유 서버·host app·기기·전역 overlay·캡처 자원별 조작 소유자를 정한다. 조율자는 결과를 통합·승인하며, 모든 검사를 직접 실행하지 않는다. - 기존 서버·사용자 session·사용자 변경을 임의로 종료·되돌리지 않는다.
examples/lynx-spa서버를 새로 시작·재시작·중지하는 일은 그 host 소유자만 한다.
문서와 예제를 작성하거나 수정하는 요청이면 seed-component의 Lynx 문서 분기를 사용한다. 이 스킬은 실행 가능한 기본 장면부터 적용하고, 나머지 범위를 구현한 뒤 최종 검증에도 사용한다.
함께 사용하는 스킬
검증 목적에 따라 필요한 스킬만 사용한다.
seed-component의 경로 조회: 실제 package, Recipe, 공개 export, 문서 예제와 SPA 소비 경로 확인seed-component의 API 비교: React와 Lynx의 공개 API, 상태, 이벤트, 접근성 차이 확인lynx-api-docs: Lynx element, layout, API 동작 확인lynx-check-css-support: CSS 속성·값의 backend와 Engine 버전 확인lynx-devtool: 온라인 검증의 CLI 사용법과 DOM, layout, console, screenshot 증거 수집analyze-video-frames: transition과 첫 렌더링의 시간축 분석
공통 실행 절차와 런타임 증거 수집은 검증 런북을 읽고 따른다. agent-lynx CLI가 기본 경로이며, DevTool MCP는 사용할 수 있을 때만 보강한다. 둘 다 사용할 수 없으면 가능한 정적 확인만 하고 native 결과는 환경 차단으로 남긴다.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 24d ago Changed 41f91cd2d5f0
- 1mo ago Changed · +6 lines 8d68c2935740
- 1mo ago Changed · -10 lines 70f6a9725c20
- 1mo ago Changed · +7 lines a5cfa1f1d69b
- 1mo ago Changed · -49 lines · -44 tokens per session fc5c36348b9d
- 1mo ago First seen · 161 lines · 82 tokens per session scan A 6cb9c355ad53
seed-verify-lynx-component is a skill published in the GitHub repository daangn/seed-design (1,180 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 3,175 once invoked, about $0.0002 per session on Opus 5.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.
bench-fixture-gen
Generates the shared per-task fixture that every competing arm starts from: a realistic dataset plus an image asset base. Fairness rule: fixtures are generated ONCE per task by this preprocessor and sealed (sha256) before any arm runs; arms never generate their own.
accessibility-per-component
Audit one design system component's accessibility against WCAG 2.2 AA: keyboard, screen reader, contrast, focus, ARIA, target size. Trigger: a11y audit, is this accessible, WCAG check, screen reader support, keyboard navigation check. Not for page- or product-wide audits.
cicd-integration
Generate CI pipeline files and check scripts (GitHub Actions, GitLab, CircleCI, Bitbucket) that automate design system checks: token validation, hardcoded values, a11y scans, visual regression, bundle size. Trigger: set up CI, quality gates, automate these checks. Not for running an audit.
schema-validator
Validate token files structurally against DTCG 2025.10 (including resolvers), Style Dictionary 3 to 5 or Tokens Studio: parse errors, $type/$value, name rules, broken or circular aliases. Trigger: validate token JSON, DTCG compliance, are my token files valid. Naming or architecture: token-audit.
sigil-audit
The auditor crawls every /docs/components/ page on the local dev server and combines static MDX analysis with a real Chromium browser pass.