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-snapshot-releasegit 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-snapshot-release)<a href="https://agentmods.dev/skills/daangn/seed-design/seed-snapshot-release"><img src="https://agentmods.dev/badge/skills/daangn/seed-design/seed-snapshot-release/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-snapshot-release"><img src="https://agentmods.dev/badge/skills/daangn/seed-design/seed-snapshot-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.00387 |
| Opus 5 | $0.00010 | $0.00193 |
| Sonnet 5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
seed-snapshot-release 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 2d 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
Snapshot Release
현재 브랜치에 연결된 PR의 snapshot release를 시작하거나 결과를 확인한다. 상세 명령·polling·실행 identity·권한 확인·결과 파싱은 Snapshot Release 런북을 따른다.
적용 조건
- PR snapshot을 새로 trigger하거나 이미 실행 중인 snapshot을 이어서 확인할 때 사용한다.
- 대상 PR과 현재 PR HEAD SHA가 먼저 확정되어야 한다.
- 대기 전용 요청에는
/snapshot댓글을 게시하지 않는다. - 명시적인 trigger 요청만 댓글 게시 승인으로 취급한다. 모호한 요청은 로컬 상태를 보여주고 확인한다.
- 댓글 게시 전 인증 계정과
OWNER,MEMBER,COLLABORATOR중 하나에 해당하는 권한 근거를 확인한다. 확인할 수 없으면 게시하지 않는다. - workflow metadata의 repository, PR number, source-sha, control-sha, run-id, run-attempt가 현재 요청과 일치할 때만 실행·artifact·결과 댓글을 재사용한다.
- 현재 PR HEAD가 바뀌었거나 metadata가 없거나 일치하지 않으면 이전 결과를 보고하지 않고 새 실행을 사용한다.
결과
성공 시 동일 실행에 연결된 📦 Snapshot Release 본문과 tarball URL을 보고한다. 실패·취소 시 failed steps와 동일 실행에 연결된 부분 결과만 보고한다.
SKILL.md에는 라우팅, 입력, 승인·중단 경계, 결과 조건만 유지한다. push, /snapshot 댓글 게시, workflow polling, run/artifact 조회의 상세 절차는 reference 문서에서 확인한다.
What ships with it
1 file 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.
- 2d ago Changed · -109 lines · -125 tokens per session c84ba9c4b74e
- 6d ago First seen · 134 lines · 144 tokens per session scan A 17eb6c17e1ad
seed-snapshot-release is a skill published in the GitHub repository daangn/seed-design (1,108 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 387 once invoked, about $0.0001 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
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers commits since the last tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.
release-readiness-check
Verify all prerequisites are met before a release by checking PRs, CI/CD status, environment health, and blocking issues across GitHub, ArgoCD, and Jira. Use before cutting a release, deploying to production, or during release planning.