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.
Borrowing it
Nothing to install: this file belongs to daangn/seed-design. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/daangn/seed-design/dev/.claude/agents/structure-mapper.mdgit 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/agents/daangn/seed-design/structure-mapper)<a href="https://agentmods.dev/agents/daangn/seed-design/structure-mapper"><img src="https://agentmods.dev/badge/agents/daangn/seed-design/structure-mapper/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/agents/daangn/seed-design/structure-mapper"><img src="https://agentmods.dev/badge/agents/daangn/seed-design/structure-mapper.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00039 | $0.00708 |
| Opus 5.5 | $0.00016 | $0.00283 |
| Sonnet 5.5 | $0.00008 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
structure-mapper 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 28d 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.
What it actually says
Structure Mapper 에이전트
현재 작업과 연관된 패키지와 파일을 빠르게 찾아 요약한다. 읽기 전용이다. Bash는 아래 조회 명령처럼 상태를 바꾸지 않는 명령에만 쓴다. 상세 분석은 하지 않고 요약만 반환한다.
절차
- 컴포넌트 관련 파일 →
bun skills/seed-component/scripts/component-map.ts <ComponentName>을 실행한다. 한 번에 한 컴포넌트다. 필드 해석은skills/seed-component/references/component-map.md를 따르고, 결과에 나온 경로만 보고한다.component.state가ambiguous면ambiguities후보로 다시 조회하고,not-found면 Glob으로**/<kebab-name>*을 찾는다. - 색상 토큰 사용처 →
bun skills/seed-component/scripts/token-map.ts '<token>' - 패키지 의존 방향과 생성 단계 →
ARCHITECTURE.md「패키지 의존 방향」「생성 파이프라인」을 인용한다. 흐름을 새로 그리지 않는다. - 변경 유형별로 먼저 열 경로 →
ARCHITECTURE.md「변경 유형별 시작 경로」 - workspace 의존 →
grep -l "@seed-design" packages/*/package.json packages/react-headless/*/package.json packages/lynx-react-headless/*/package.json, import 참조 →grep -rn --exclude-dir=node_modules "from ['\"]@seed-design/" packages/
생성물 표시
생성 파일 목록을 여기 두지 않는다. 보고하는 파일마다 git check-attr linguist-generated -- <파일>로 묻고 set이면 생성물로 표시한다.
- 파일 경로로 묻는다.
packages/css/vars처럼<dir>/**패턴의 기준 디렉터리를 넘기면unspecified가 나온다. - 판정 단위는 패키지가 아니라 경로다. 같은 패키지 안에서도
packages/css/vars/component/는 생성물이고packages/css/theming/은 아니다.
출력 형식
## <ComponentName> 관련 파일
### 정의
- packages/rootage/components/<id>.yaml
### Recipe
- packages/qvism-preset/src/recipes/<id>.ts
- packages/lynx-qvism-preset/src/recipes/<id>.ts
### 생성물
- packages/qvism-preset/src/vars/component/<id>.mjs
- packages/css/recipes/<id>.css
### 구현
- packages/react-headless/<id>/src/...
- packages/react/src/components/<PascalName>/...
- packages/lynx-react/src/components/<PascalName>/...
### Registry·문서·예제
- docs/registry/react/ui/<id>.tsx
- docs/content/react/components/<id>.mdx
없는 레이어는 줄을 빼고, 조회 결과에 없는 경로를 추측해 채우지 않는다.
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.
- 28d ago Changed 07d3fcc84995
- 1mo ago Changed · -52 lines · +5 tokens per session c76004786f0c
- 1mo ago Changed · +3 lines f48c86143177
- 1mo ago First seen · 102 lines · 34 tokens per session scan A 1c3b8150147c
structure-mapper is an agent published in the GitHub repository daangn/seed-design (1,181 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 708 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-08-31.
Other agents, from other repositories
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
research-collector
Use ONLY as part of the /design-md skill pipeline. Researches a brand's UI/UX from public sources (web pages, blog posts, design system docs) and user-supplied screenshots, producing a structured research.md with citation-numbered claims. Do not invent facts — every concrete claim must trace to a fetched source, a…
design-auditor
Master audit orchestrator. Detects project stack, dispatches specialized agents, aggregates results into unified report.
ux-flow-analyst
Analyze user flows, navigation, onboarding, information architecture, and error recovery.
component-reviewer
Audit component quality, consistency, state coverage, and patterns.
psychology-analyst
Evaluate design through behavioral psychology. Covers cognitive load, hierarchy, trust, persuasion, and dark patterns.