svelte-lsp: Instructions file for Claude Code

CLAUDE.md

svelte-lsp CLAUDE.md is an instructions file for Claude Code from zircote/svelte-lsp. It costs 612 tokens per session, scanned A, original, MIT.

Project instructions for developing Svelte applications with the Svelte language server, formatting, linting, and type checking. Svelte is a web framework for building user interfaces.

In plain words
What is it for?
Use them when working on a Svelte project to set up development tools, run formatting and checks, and understand its files, hooks, and setup command.
Why use it?
They give the agent project-specific guidance and describe checks that can run after Svelte files are changed.

Instructions file for Claude Code

Written for Claude Code: PostToolUse hook event. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is zircote/svelte-lsp's own configuration. It tells Claude Code how to work on svelte-lsp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything svelte-lsp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to zircote/svelte-lsp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zircote/svelte-lsp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/zircote/svelte-lsp

Made for: Claude Code.

Wrote 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.

agentmods badge for svelte-lsp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/zircote/svelte-lsp/claude-md.svg)](https://agentmods.dev/instructions/zircote/svelte-lsp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/zircote/svelte-lsp/claude-md"><img src="https://agentmods.dev/badge/instructions/zircote/svelte-lsp/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 612 This file is loaded in full into every session.
When invoked 612 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00612 $0.00612
Opus 5 $0.00306 $0.00306
Sonnet 5 $0.00122 $0.00122
Haiku 4.5 $0.00061 $0.00061

Measured 7d ago against content hash 59e97c2d6a4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

svelte-lsp CLAUDE.md 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.

CLAUDE.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

A Claude Code plugin providing Svelte development support through svelte-language-server LSP integration and automated hooks for formatting, linting, and type checking.

Setup

Run /setup to install all required tools, or manually:

# Global LSP server
npm install -g svelte-language-server

# Project development tools
npm install -D svelte-check prettier prettier-plugin-svelte eslint eslint-plugin-svelte

Key Files

File Purpose
.lsp.json svelte-language-server configuration
hooks/hooks.json Automated development hooks
commands/setup.md /setup command definition
.claude-plugin/plugin.json Plugin metadata

Hook System

All hooks trigger on PostToolUse after Write|Edit operations. Hooks use graceful degradation when optional tools aren't installed.

Hook categories:

  • Formatting (.svelte): Prettier with svelte plugin
  • Type Checking (.svelte): svelte-check for component validation
  • Linting (.svelte): ESLint with svelte plugin
  • Hints (.svelte): TODO/FIXME detection

When Modifying Hooks

Edit hooks/hooks.json. The hooks use Claude Code's standard event-based format:

{
    "hooks": {
        "PostToolUse": [
            {
                "matcher": "Write|Edit",
                "hooks": [{ "type": "command", "command": "..." }],
                "conditions": { "fileExtensions": [".svelte"] }
            }
        ]
    }
}

Best practices:

  • Use || true to prevent hook failures from blocking writes
  • Use head -N to limit output verbosity
  • Use command -v tool >/dev/null && for optional tool dependencies
  • Use npx to run local node_modules binaries

Svelte-Specific Guidance

Component Structure

Svelte components use three sections:

  • <script> - Component logic (JavaScript/TypeScript)
  • <style> - Scoped CSS
  • Markup - HTML with Svelte syntax

Read the full file on GitHub · 87 lines

Changes

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.

  1. 7d ago First seen · 87 lines · 612 tokens per session scan A 59e97c2d6a4c

Subscribe to this mod's changes

svelte-lsp CLAUDE.md is an instructions file published in the GitHub repository zircote/svelte-lsp (5 stars, last pushed 28d ago), licensed MIT. It adds 612 tokens to every session, about $0.0031 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.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens