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 HirogaKatageri/hirokata --skill svelte-best-practicesgit clone --depth 1 https://github.com/HirogaKatageri/hirokataWrote 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/hirogakatageri/hirokata/svelte-best-practices)<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/svelte-best-practices"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/svelte-best-practices/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/hirogakatageri/hirokata/svelte-best-practices"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/svelte-best-practices.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.00111 | $0.02828 |
| Opus 5 | $0.00056 | $0.01414 |
| Sonnet 5 | $0.00022 | $0.00566 |
| Haiku 4.5 | $0.00011 | $0.00283 |
Grade A, and why
svelte-best-practices 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Svelte 5 / SvelteKit — Best Practices
Cross-cutting guidance: how to choose the right primitives, keep apps fast and accessible, and write code that doesn't break in production.
State Management Strategy
Pick the smallest scope that works:
- Component-local —
let x = $state(0)inside a.sveltefile. Default for anything not shared. - Per-feature module —
.svelte.tsexporting an object with mutable fields (export const counter = $state({ value: 0 })). Default for cross-component state in a feature. - Context —
setContext/getContextfor tree-scoped state where multiple components need a per-instance shared object (e.g., a form, a dropdown). Pair context with a reactive$stateobject so the value can update. - URL — for state that should survive reloads, deep-link, or affect SSR (filters, pagination, tabs). Read via
page.url.searchParams, write viagoto('?x=1', { replaceState: true, keepFocus: true, noScroll: true }). - Cookies / DB — for state that crosses sessions or needs server enforcement. Set in form actions /
+server/ hooks; read in serverload.
Avoid:
- Global module-level singletons that get reassigned (the rune transform breaks across module boundaries — see
svelte-core"Sharing State Across Modules"). - Putting per-request server state in module scope — SvelteKit reuses module instances across requests, so anything you write to a module-level variable from a load function leaks between users.
- Mixing legacy
writablestores with runes in the same feature unless you have a migration reason.
Server-Only Modules
Three rules:
- Anything in
$lib/server/**is server-only — importing it from a+page.svelteor any*.client.*is a build error. +page.server.ts,+layout.server.ts,+server.ts,hooks.server.tsare server-only.$env/static/privateand$env/dynamic/privateare server-only.
When unsure, check whether a secret could leak. If it could, it goes server-side.
Performance
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 · 276 lines · 111 tokens per session scan A 777f2a8feab7
svelte-best-practices is a skill published in the GitHub repository HirogaKatageri/hirokata (5 stars, last pushed 2d ago), licensed MIT. It adds 111 tokens to every session and 2,828 once invoked, about $0.0006 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.