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 agentlas-ai/agentlas-desktop --skill seed-designgit clone --depth 1 https://github.com/agentlas-ai/agentlas-desktopWrote 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/agentlas-ai/agentlas-desktop/seed-design)<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/seed-design"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/seed-design.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.1 | $0.00035 | $0.00332 |
| Opus 5 | $0.00017 | $0.00166 |
| Sonnet 5 | $0.00007 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
seed-design 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 8d 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
Skill Purpose
Serves as the single source of truth for the SEED Design system, routing to official documentation for component specifications, platform setup, migrations, and health diagnostics (Doctor).
Preconditions
- A SEED Design-related question, component implementation request, foundation inquiry, or codebase diagnostic is requested.
- References
$doctor,$doctor-react,$doctor-lynx,$migration, and$upgrade.
Steps
- Classify Request:
- Common component specifications and Foundations (platform-agnostic).
- Platform implementation for React or Lynx.
- Doctor diagnostics and codebase migration.
- Determine Platform: Check user input →
seed-design.jsonconfiguration → direct package dependencies (@seed-design/*). - Route to Official Docs:
- Query
https://seed-design.io/llms.txtand platform indices to read authoritative leaf documentation.
- Query
- Execute Doctor (if requested):
- Perform read-only inspection according to
$doctorto diagnose package compatibility, snippet hygiene, and token contracts. - Output structured findings with remediation prompts.
- Perform read-only inspection according to
Outputs
- Authoritative design system specifications and implementation guidance.
- Diagnostic YAML/HTML reports in temporary directories when running Doctor.
Verification
- Ensure all technical guidance aligns with the official live documentation index.
- Verify that diagnostic operations operate in read-only mode without mutating the target repository unexpectedly.
What ships with it
10 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.
- references/component-guidelines.md 5.1 KB
- references/foundation-contract.md 1.8 KB
- references/library-authors.md 2.1 KB
- references/no-deprecated-component.md 2.4 KB
- references/outdated-version.md 1.7 KB
- references/package-compatibility.md 1.8 KB
- references/project-config.md 2.5 KB
- references/project-setup.md 1.7 KB
- references/snippet-compatibility.md 1.7 KB
- references/snippet-generation.md 1.8 KB
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.
- 8d ago First seen · 32 lines · 35 tokens per session scan A 20a4962b2a46
seed-design is a skill published in the GitHub repository agentlas-ai/agentlas-desktop (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 332 once invoked, about $0.0002 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 skills, from other repositories
figma-implement-design
Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via…
build-dashboard
Build the visual layer of a holaOS dashboard app — TanStack Start + @holaboss/ui + workspace tokens. Use when an app has SDK primitives wired (via app-builder-sdk) AND needs a src/client/ UI surface. NOT for marketing pages, NOT for snapshot HTML reports.
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics.
figma
Complete guide for the Figma plugin — REST API access, real-time selection monitoring via CDP, and the figma-app interactive UI. Read this IMMEDIATELY when the user asks to work with Figma.
architecture-diagram
How to draw and maintain the architecture diagram Ensemblr keeps for a workspace — ensemblrgetarchitecturediagram to fetch the stored one (it answers with null when nobody has drawn this workspace yet), the IR shape, how to derive it from the codebase, and ensemblrupdatearchitecturediagram to store it. Read this when…