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 Michael-Obele/shadcn-svelte-mcp --skill shadcn-sveltekit-designgit clone --depth 1 https://github.com/Michael-Obele/shadcn-svelte-mcpWrote 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/michael-obele/shadcn-svelte-mcp/shadcn-sveltekit-design)<a href="https://agentmods.dev/skills/michael-obele/shadcn-svelte-mcp/shadcn-sveltekit-design"><img src="https://agentmods.dev/badge/skills/michael-obele/shadcn-svelte-mcp/shadcn-sveltekit-design/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/michael-obele/shadcn-svelte-mcp/shadcn-sveltekit-design"><img src="https://agentmods.dev/badge/skills/michael-obele/shadcn-svelte-mcp/shadcn-sveltekit-design.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.00099 | $0.01043 |
| Opus 5 | $0.00049 | $0.00522 |
| Sonnet 5 | $0.00020 | $0.00209 |
| Haiku 4.5 | $0.00010 | $0.00104 |
Grade A, and why
shadcn-sveltekit-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 13d 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shadcn SvelteKit Design
Use this skill to create polished SvelteKit UI while grounding component decisions in the configured shadcn-svelte MCP instead of memory.
Preconditions
- Expect these MCP tools to be available:
shadcn-svelte-search,shadcn-svelte-get,shadcn-svelte-list,shadcn-svelte-icons, andbits-ui-get. - If the MCP is missing, say that clearly, help the user configure it, and avoid pretending a component or API exists.
- Treat
shadcn-svelte-getas the source of truth for any component, block, chart, or docs page you plan to use. - Treat official shadcn-svelte CLI installation as the default path for any library component that exists upstream.
Workflow
-
Understand the target before designing. Ask for the screen type, audience, content density, brand direction, and whether the work should preserve an existing visual language or introduce a new one.
-
Discover before composing. If the user describes a feature vaguely, start with
references/mcp-workflow.mdand use the discovery tools before writing UI code. -
Commit to an intentional visual direction. Pick a clear design thesis instead of drifting into generic SaaS UI. Define typography, color logic, spacing, hierarchy, and motion up front.
-
Map the design to verified primitives. Build the layout from components, blocks, charts, docs, and icons that the MCP confirms are real. If the desired component is not available, say so and propose the closest verified alternative.
-
Write Svelte-first code. Output valid SvelteKit and Svelte 5 code. Never use React props, JSX patterns, or shadcn/ui React guidance.
-
Explain the chosen building blocks. Mention which components or docs were verified, especially when the user asks for implementation guidance or installation commands.
-
Install vendor components instead of reimplementing them. If a verified shadcn-svelte component exists, fetch the official CLI command from the MCP when possible and run it yourself when the task requires editing the project. Fall back to official shadcn-svelte documentation only when the MCP is unavailable. Do not hand-write the upstream component source from scratch. It is fine to write wrappers, compositions, page code, or project-specific variants around installed components.
What ships with it
3 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.
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.
- 13d ago First seen · 77 lines · 99 tokens per session scan A d05d40a80fb0
shadcn-sveltekit-design is a skill published in the GitHub repository Michael-Obele/shadcn-svelte-mcp (58 stars, last pushed 2d ago), licensed MIT. It adds 99 tokens to every session and 1,043 once invoked, about $0.0005 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-30.
Other skills, from other repositories
dryui-build
Builds and edits Svelte 5 user interfaces with DryUI components, layout hooks, theme tokens, and accessibility rules. Use when creating or modifying app UI, pages, routes, forms, dashboards, component compositions, visual polish, or design-to-code work with @dryui/ui.
dryui-build
Builds and edits Svelte 5 user interfaces with DryUI components, layout hooks, theme tokens, and accessibility rules. Use when creating or modifying app UI, pages, routes, forms, dashboards, component compositions, visual polish, or design-to-code work with @dryui/ui.
shadcn-svelte
Manages shadcn-svelte components and projects — adding, updating, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn-svelte, the CLI, design-system presets, or any project with a components.json file. Also triggers for…
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality and accessible markup. Use this skill when the user asks to build or beautify web components, pages, applications, landing pages, dashboards, artifacts, or React/HTML/CSS UI. Generates creative, polished code that avoids generic AI…
dryui-build
Experimental DryUI layout-only skill that extracts responsive page structure from design images as abstract colored blocks with strict shell areas, fixed page container queries, and visual self-checks. Use when testing design-image to layout-skeleton extraction.
dryui-build
Experimental DryUI page-layout skill that builds colored block page prototypes with mobile-first container queries. Use when testing page layout, responsive regions, dashboards, shells, or full-page structure before detailed UI styling.