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 fubits1/svelte-skills --skill migration-svelte-5git clone --depth 1 https://github.com/fubits1/svelte-skillsWrote 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/fubits1/svelte-skills/migration-svelte-5)<a href="https://agentmods.dev/skills/fubits1/svelte-skills/migration-svelte-5"><img src="https://agentmods.dev/badge/skills/fubits1/svelte-skills/migration-svelte-5/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/fubits1/svelte-skills/migration-svelte-5"><img src="https://agentmods.dev/badge/skills/fubits1/svelte-skills/migration-svelte-5.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.00065 | $0.03184 |
| Opus 5 | $0.00032 | $0.01592 |
| Sonnet 5 | $0.00013 | $0.00637 |
| Haiku 4.5 | $0.00006 | $0.00318 |
Grade A, and why
migration-svelte-5 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 11d 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Svelte 3/4 to 5 Migration
Authoritative reference: the official Svelte 5 migration guide is the canonical list of breaking changes and gotchas (components are no longer classes → mount/hydrate; $effect is client-only; event-modifier limits; and the rest). This skill is the migration WORKFLOW — order, audit, interop, traps; defer to the guide for the full what-changed.
Required companion skills
Invoke these at the indicated points. This skill says WHEN; they say HOW.
| Skill | When | Source |
|---|---|---|
svelte:svelte-code-writer |
Before writing/editing ANY .svelte or .svelte.ts |
plugin: svelte/svelte |
svelte:svelte-core-bestpractices |
Before writing ANY Svelte 5 component logic | plugin: svelte/svelte |
svelte-5:code-style-svelte |
After every .svelte file edit |
this marketplace |
frontend:code-style |
After every file edit | this marketplace |
frontend:editing |
During every code edit | this marketplace |
svelte-5:doc-component |
After creating or migrating a .svelte component |
this marketplace |
svelte-5:storybook |
When creating/updating stories | this marketplace |
svelte-5:storybook-vitest |
When writing play functions | this marketplace |
svelte-5:testing-svelte |
When writing vitest browser tests | this marketplace |
frontend:playwright |
Before AND after migration (baselines + verification) | this marketplace |
frontend:pixel-perfect |
For any CSS/layout changes during migration | this marketplace |
frontend:validate-file |
After EVERY file edit | this marketplace |
frontend:migration |
Framework-agnostic phases this skill builds on | this marketplace |
Prefer delegating each .svelte create/edit/review to the svelte:svelte-file-editor subagent (plugin svelte/svelte). It runs in its own context window, so its docs lookup and autofixer iteration don't spend the main agent's context during a long migration. The companion skills above still say WHEN; the subagent is where the per-file edit happens.
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.
- 11d ago First seen · 311 lines · 65 tokens per session scan A 1fe4874f518a
migration-svelte-5 is a skill published in the GitHub repository fubits1/svelte-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 3,184 once invoked, about $0.0003 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
shadcn-svelte
Pre-built shadcn-svelte components for json-render Svelte apps. Use when working with @json-render/shadcn-svelte, adding standard UI components to a Svelte catalog, or building Svelte web UIs with shadcn-svelte + Tailwind CSS components.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
v3-create-crud
A page generator for standard create, read, update, and delete screens, commonly called CRUD screens. It uses Element Plus, a Vue user-interface library, to build tables, searches, pagination, forms, and delete confirmations.
v3-use-composables
Documentation for reusable Vue functions in a project, covering device detection, asynchronous dropdown data, loading screens, pagination, routing, themes, page titles, and watermarks.
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.
moai-domain-frontend
Frontend development specialist covering React 19, Next.js 16, Vue 3.5, and modern UI/UX patterns with component architecture. Use when building web UIs, implementing components, optimizing frontend performance, or integrating state management.