seed-component

seed-component is a skill for Codex from daangn/seed-design. It costs 72 tokens per session (721 once invoked), scanned A, original, Apache-2.0.

A workflow for finding, comparing, implementing, and documenting SEED design-system components across React and Lynx, a cross-platform UI framework. It also covers colour-token inspection and accessibility contrast checks.

In plain words
What is it for?
Use it to locate a component, compare React and Lynx APIs, plan a new component, port one between platforms, or investigate colour-token contrast.
Why use it?
It keeps new or changed components aligned with existing APIs, styles, documentation, and platform behaviour instead of creating disconnected implementations.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to locate a component, compare React and Lynx APIs, plan a new component, port one between platforms, or investigate colour-token contrast.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/daangn/seed-design/seed-component
About the project

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.

daangn/seed-design · 1,180 stars · on GitHub · seed-design.io

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.

Any agent
npx skills add daangn/seed-design --skill seed-component
Clone the repo
git clone --depth 1 https://github.com/daangn/seed-design

Made for: Codex.

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 seed-component

README.md
[![agentmods](https://agentmods.dev/badge/skills/daangn/seed-design/seed-component/github.svg)](https://agentmods.dev/skills/daangn/seed-design/seed-component)
Your own site
<a href="https://agentmods.dev/skills/daangn/seed-design/seed-component"><img src="https://agentmods.dev/badge/skills/daangn/seed-design/seed-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.

agentmods 80×15 button for seed-component

Your own site · 80×15
<a href="https://agentmods.dev/skills/daangn/seed-design/seed-component"><img src="https://agentmods.dev/badge/skills/daangn/seed-design/seed-component.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 721 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.00072 $0.00721
Opus 5.5 $0.00029 $0.00288
Sonnet 5.5 $0.00014 $0.00144
Haiku 4.5 $0.00007 $0.00072

Measured 24d ago against content hash 52e92375a364, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

seed-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.

The scan reads SKILL.md. This mod also ships 5 executable files (scripts/api-parity.ts, scripts/component-map.ts, scripts/scaffold-plan.ts, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/seed-component/SKILL.md · 27 lines

What it actually says

SEED 컴포넌트

요청이 원하는 결과로 분기를 하나 고르고, 그 분기의 reference만 읽는다. 조회·비교·토큰 분기는 읽기 전용이다. 결과를 반환하고 끝내며, 사용자가 구현을 요청하지 않는 한 다른 분기로 넘어가지 않는다.

요청 결과 읽을 reference 실행
한 컴포넌트의 구현·export·Registry·문서·테스트 경로만 component-map.md bun skills/seed-component/scripts/component-map.ts <Component>
React·Lynx 공개 API와 사용자 결과 차이만 api-parity.md bun skills/seed-component/scripts/api-parity.ts <Component>
색상 토큰의 정의·alias·사용처·생성 표면 또는 대비만 (컴포넌트 없이도) color-token-analysis.md bun skills/seed-component/scripts/token-map.ts '<token>', token-contrast.ts
새 컴포넌트 또는 한 플랫폼이 없는 포팅 implementation-workflow.md 신규·포팅 bun skills/seed-component/scripts/scaffold-plan.ts
기존 컴포넌트의 구현·동작·구조 변경 implementation-workflow.md 기존 구현 변경 경로 조회 후 필요 시 API 비교
Lynx 문서·실행 예제만 (컴포넌트 동작 유지) lynx-docs.md 경로가 불명확할 때만 경로 조회
React 문서·예제, Storybook, 생성물만 implementation-workflow.md 짧은 경로 경로가 불명확할 때만 경로 조회

경계

  • 문서·Storybook 전용 분기는 컴포넌트 구현을 요구하지 않는다. 실제 호스트 앱에서도 재현되는 API·동작 문제를 발견하면 문서용 우회 대신 기존 구현 변경으로 전환한다.
  • 새 패키지, 외부 의존성, CI 설정이 필요하면 구현 전에 사용자 확인을 받는다.
  • Lynx native 결과를 소스 수정 없이 독립 판정하는 일은 seed-verify-lynx-component가 맡는다.
  • 여러 레이어의 담당·병렬 작업·에이전트 간 협의가 요청됐거나 필요하면 seed-orchestrate-component를 함께 사용한다.
  • changeset·변경 계획·제출은 seed-change가 맡는다.
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. 24d ago First seen · 27 lines · 72 tokens per session scan A 52e92375a364

Subscribe to this mod's changes

seed-component is a skill published in the GitHub repository daangn/seed-design (1,180 stars, last pushed today), licensed Apache-2.0. It adds 72 tokens to every session and 721 once invoked, about $0.0003 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-23.

Related

Other skills, from other repositories

ss-learn

Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule…

bitjaru/styleseed · 73 tokens

ui-components

UI component library patterns for shadcn/ui and Radix Primitives. Use when building accessible component libraries, customizing shadcn components, using Radix unstyled primitives, or creating design system foundations.

yonatangross/orchestkit · 44 tokens

s2-docs

Look up Spectrum 2 (S2) component documentation, design guidelines, and usage patterns when building with React Spectrum or Spectrum Web Components. Use when the user mentions Spectrum, S2, React Spectrum, RSP, Spectrum Web Components, or SWC, or names a Spectrum component (Button, Picker, ComboBox, TextField…

adobe/spectrum-design-data · 91 tokens

sigil-migration

Before migrating, audit the existing project.

Kevin-Liu-01/Sigil-UI · 4 tokens

sigil-component

Every Sigil component lives in packages/components/src/ and follows this pattern.

Kevin-Liu-01/Sigil-UI · 3 tokens

instui-docs

Look up authoritative Instructure UI (InstUI, @instructure/ui-) documentation — component APIs, props, theme variables, usage examples, and guides — by querying instructure.design's plaintext docs. Use whenever the user asks how to use an InstUI component, which props/prop types exist, how to theme/style it…

instructure/instructure-ui · 97 tokens