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 agentmods add commands/daangn/seed-design/check-docs-consistencygit 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/commands/daangn/seed-design/check-docs-consistency)<a href="https://agentmods.dev/commands/daangn/seed-design/check-docs-consistency"><img src="https://agentmods.dev/badge/commands/daangn/seed-design/check-docs-consistency.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.00006 | $0.00196 |
| Opus 5 | $0.00003 | $0.00098 |
| Sonnet 5 | $0.00001 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
check-docs-consistency 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 today.
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
문서 일관성 확인
seed-component-map 스킬로 각 컴포넌트의 현재 경로를 수집합니다. full 또는 props-only 모드에서는 seed-api-parity도 사용하고, 확인하지 못한 차원은 추측하지 말고 unknown으로 보고합니다.
인자
- $COMPONENT_ID: 선택 사항. 생략하면 전체를 확인합니다.
- $MODE: 선택 사항.
full|props-only|existence-only
필수 결과
- 이름, 설명, props, component id의 일관성을 보고합니다.
- 누락된 파일과 중요한 불일치를 보고합니다.
- 컴포넌트별 상태를
OK,WARN,ERROR중 하나로 짧게 표시합니다.
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.
- today Changed 9c7190b0d91b
- 4d ago First seen · 20 lines · 6 tokens per session scan A c61c0505eae9
check-docs-consistency is a command published in the GitHub repository daangn/seed-design (1,084 stars, last pushed today), licensed Apache-2.0. It adds 6 tokens to every session and 196 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
verify
Fidelity check — rebuild a page from the extracted tokens, pixel-diff it against the live site, and score how faithfully the tokens capture the design.
battle
Head-to-head graded battle card between two sites — eight dimensions, bar-by-bar, verdict line.
critique-screen
Run all seven visual critiques on a screen and output a prioritised fix list.
critique-ux
Run a focused UX critique on a screen — affordances, information density, and hierarchy — and output a prioritised fix list.
design-onboarding
Design a first-run experience end to end — activation path, progressive disclosure, and time to first value.
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.