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 agentmods add instructions/weise25/localsite-ai/agents-mdgit clone --depth 1 https://github.com/weise25/LocalSite-aiWrote 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/instructions/weise25/localsite-ai/agents-md)<a href="https://agentmods.dev/instructions/weise25/localsite-ai/agents-md"><img src="https://agentmods.dev/badge/instructions/weise25/localsite-ai/agents-md.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.01777 | $0.01777 |
| Opus 5 | $0.00889 | $0.00889 |
| Sonnet 5 | $0.00355 | $0.00355 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade A, and why
LocalSite-ai AGENTS.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 6d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are able to use the Svelte MCP server, where you have access to comprehensive Svelte 5 and SvelteKit documentation. Here's how to use the available tools effectively:
Available Svelte MCP Tools:
1. list-sections
Use this FIRST to discover all available documentation sections. Returns a structured list with titles, use_cases, and paths. When asked about Svelte or SvelteKit topics, ALWAYS use this tool at the start of the chat to find relevant sections.
2. get-documentation
Retrieves full documentation content for specific sections. Accepts single or multiple sections. After calling the list-sections tool, you MUST analyze the returned documentation sections (especially the use_cases field) and then use the get-documentation tool to fetch ALL documentation sections that are relevant for the user's task.
3. svelte-autofixer
Analyzes Svelte code and returns issues and suggestions. You MUST use this tool whenever writing Svelte code before sending it to the user. Keep calling it until no issues or suggestions are returned.
4. playground-link
Generates a Svelte Playground link with the provided code. After completing the code, ask the user if they want a playground link. Only call this tool after user confirmation and NEVER if code was written to files in their project.
Project Overview
LocalSite-AI generates complete, self-contained HTML/CSS/JS web pages from natural language prompts using AI. Users pick a provider and model, describe what they want, and get a live preview with an editable Monaco code editor.
Tech stack: SvelteKit 2, Svelte 5 (runes), Deno 2, Tailwind CSS 3, Vercel AI SDK v5, Monaco Editor, Paneforge, svelte-sonner, @lucide/svelte.
Runtime: Deno 2 (deno task dev/build/check/lint). package.json retains
npm scripts for compatibility but Deno is the primary toolchain.
Architecture
src/
routes/
+page.svelte Main page: WelcomeView -> GenerationView
+layout.svelte Global layout, Toaster
+layout.ts SSR disabled (ssr = false)
+error.svelte Error boundary
api/
generate-code/+server.ts POST: streams NDJSON (text + reasoning)
get-models/+server.ts GET: models for provider; POST: list providers
get-default-provider/+server.ts GET: default provider from env
lib/
state/
code-generation.svelte.ts CodeGeneration class (rune-based state)
server/providers/
config.ts LLMProvider enum, config registry, env helpers
provider.ts 9 provider client classes, generateCodeStream()
prompts.ts DEFAULT_SYSTEM_PROMPT, THINKING_SYSTEM_PROMPT
components/
[see README for full component list]
ui/ 8 hand-rolled primitives (Button, Select, etc.)
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.
- 6d ago First seen · 164 lines · 1,777 tokens per session scan A 69afd706da22
LocalSite-ai AGENTS.md is an instructions file published in the GitHub repository weise25/LocalSite-ai (401 stars, last pushed 2mo ago), licensed MIT. It adds 1,777 tokens to every session, about $0.0089 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-30.
Other instructions, from other repositories
tiptap tiptap.instructions.md
Instructions for ueberdosis/tiptap, covering tiptap, what is tiptap, repository layout, npm scripts and linting & formatting.
daisyui packages.docs.instructions.md
Instructions for saadeghi/daisyui, a project described as: 🌼 🌼 🌼 🌼 🌼 The most popular, free and open-source Tailwind CSS component library.
tiny-vue AGENTS.md
AGENTS.md instructions for opentiny/tiny-vue, covering agents.md, 项目概述, 关键目录结构, 环境要求 and 核心命令.
vue-tui AGENTS.md
AGENTS.md instructions for vuejs-ai/vue-tui, covering common pitfalls & best practices, project context records (pcr), using vite+, the unified toolchain for the web and review checklist.
skills AGENTS.md
AGENTS.md instructions for vuejs-ai/skills, covering vue skills development guide, branch strategy, development workflow, skill scopes and common pitfalls & best practices.
mulmoterminal CLAUDE.md
Claude Code instructions for receptron/mulmoterminal, covering claude.md — mulmoterminal, stack & package manager, run after changes, import a component at module scope, never inside a test and no emojis.