Borrowing it
Nothing to install: this file belongs to opennem/openelectricity. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opennem/openelectricity/main/.agents/skills/svelte-code-writer/SKILL.mdgit clone --depth 1 https://github.com/opennem/openelectricityWrote 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/opennem/openelectricity/svelte-code-writer)<a href="https://agentmods.dev/skills/opennem/openelectricity/svelte-code-writer"><img src="https://agentmods.dev/badge/skills/opennem/openelectricity/svelte-code-writer.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.00068 | $0.00524 |
| Opus 5 | $0.00034 | $0.00262 |
| Sonnet 5 | $0.00014 | $0.00105 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
svelte-code-writer 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 7d 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.
This is a copy
100% identical to svelte-code-writer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
CLI tools
You have access to @sveltejs/mcp CLI for Svelte-specific assistance. Use these commands via npx:
List documentation sections
npx @sveltejs/mcp list-sections
Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths.
Get documentation
npx @sveltejs/mcp get-documentation "<section1>,<section2>,..."
Retrieves full documentation for specified sections. Use after list-sections to fetch relevant docs.
Example:
npx @sveltejs/mcp get-documentation "$state,$derived,$effect"
Svelte autofixer
npx @sveltejs/mcp svelte-autofixer "<code_or_path>" [options]
Analyzes Svelte code and suggests fixes for common issues.
Options:
--async- Enable async Svelte mode (default: false)--svelte-version- Target version: 4 or 5 (default: 5)
Examples:
# Analyze inline code (escape $ as \$)
npx @sveltejs/mcp svelte-autofixer '<script>let count = \$state(0);</script>'
# Analyze a file
npx @sveltejs/mcp svelte-autofixer ./src/lib/Component.svelte
# Target Svelte 4
npx @sveltejs/mcp svelte-autofixer ./Component.svelte --svelte-version 4
Important: When passing code with runes ($state, $derived, etc.) via the terminal, escape the $ character as \$ to prevent shell variable substitution.
Workflow
- Uncertain about syntax? Run
list-sectionsthenget-documentationfor relevant topics - Reviewing/debugging? Run
svelte-autofixeron the code to detect issues - Always validate - Run
svelte-autofixerbefore finalizing any Svelte component
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.
- 7d ago First seen · 65 lines · 68 tokens per session scan A ccd435bc524f
svelte-code-writer is a skill published in the GitHub repository opennem/openelectricity (10 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 524 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to svelte-code-writer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
svelte
Svelte 5 - Reactive UI framework with compiler magic, Runes API, SvelteKit full-stack framework, SSR/SSG, minimal JavaScript.
svelte-expert
Expert knowledge in Svelte framework, SvelteKit, reactivity system, compiled approach, and building performant web applications. Use when the user mentions SvelteKit, reactivity, compiler, frontend, performance, or JavaScript, or when the task involves Svelte Fundamentals, Reactivity System, Installation and Setup, or…
svelte-docs
Svelte 5.x + SvelteKit 2.x — runes, components, stores, transitions, SSR, routing, TypeScript.
sveltekit
SvelteKit - Full-stack Svelte framework with file-based routing, SSR/SSG, form actions, and adapters for deployment.
svelte
Svelte 5 - Reactive UI framework with compiler magic, Runes API, SvelteKit full-stack framework, SSR/SSG, minimal JavaScript.
with-svelte
Modern Svelte 5 + SvelteKit guidance and routing. Use whenever creating, editing, reviewing, or debugging a Svelte component (.svelte) or module (.svelte.ts/.svelte.js), or any SvelteKit project. Covers runes ($state, $derived, $effect, $props, $bindable), template directives ({@attach}, {@render}, {@html}, snippets…