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 composition-sveltegit 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/composition-svelte)<a href="https://agentmods.dev/skills/fubits1/svelte-skills/composition-svelte"><img src="https://agentmods.dev/badge/skills/fubits1/svelte-skills/composition-svelte/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/composition-svelte"><img src="https://agentmods.dev/badge/skills/fubits1/svelte-skills/composition-svelte.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.00057 | $0.01800 |
| Opus 5 | $0.00028 | $0.00900 |
| Sonnet 5 | $0.00011 | $0.00360 |
| Haiku 4.5 | $0.00006 | $0.00180 |
Grade A, and why
composition-svelte 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 10d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
composition-svelte
Decompose a Svelte 5 feature by ROLE. Wrong role assignment is the root cause of every architectural fuckup. Before generating files, pin three decisions: composition shape, snippet API, state location. Per-file contracts fall out from those.
Rules from frontend:code-style, svelte-5:code-style-svelte, frontend:editing, svelte:svelte-code-writer, svelte:svelte-core-bestpractices apply throughout. Run mcp__svelte__svelte-autofixer after every .svelte edit.
When to use
- Designing a wrapper / Provider-style component (popup, menu, drawer, modal, tooltip, panel, slide-in, accordion)
- Autofixer flagged
bind:this - About to type
$effect(() => { new ThirdPartyThing(...) }) - About to write
prop={appState.x}orprop={someStore.value} - Naming a new file
Default.svelte/Feature.svelte/Wrapper.svelte - Calling
setDOMContent/appendChild(svelteRenderedNode)/ similar - Deciding default vs named snippets
- Fixing a focus / ESC / keyboard bug in one of several similar menus
- About to add a maplibre
Marker, leafletL.marker, d3 selection - About to type
:global(...)inside a wrapper's<style>block
Skip for: CSS-only tweaks, test-only edits, backend / non-Svelte work.
Pin three decisions first
Answer in writing BEFORE generating files. Full tables and pointers in references/decisions.md.
- Shape: Composition shape / Non-Svelte Host?
- Snippet API: default
children, named snippets, or mix? - State location: where each piece of state lives. Options can coexist; pick what fits each piece.
.svelte.tsmodules (module-level$stateexports, classes with$statefields), component-local$state, context (createContext), existing global state.
If intent is ambiguous, ask via AskUserQuestion, never infer silently.
Quick reference
| Need | Read |
|---|---|
| Picking shape and snippet/state design | references/decisions.md |
| Composition shape, seven-role contract + folder structure (covers both caller-content and view-dispatcher / Provider behaviour) | references/composition-shape.md |
| Non-Svelte Host shape | references/non-svelte-host.md |
| Lifecycle rune choice | references/lifecycle.md |
| Bridging to a third-party DOM library | references/third-party.md |
A11y for overlays (focus, ESC, :focus-visible) |
references/a11y-overlays.md |
CSS scope (avoiding :global()) |
references/css-scope.md |
| Counter-arguments for common rationalizations | references/rationalizations.md |
What ships with it
8 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.
- 10d ago First seen · 105 lines · 57 tokens per session scan A 9917e4180aff
composition-svelte is a skill published in the GitHub repository fubits1/svelte-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 1,800 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.
frontend-conventions
Frontend convention reference (SvelteKit / Svelte 5). Auto-injected into frontend-aware agents - not user-invocable.