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 agents/bobmatnyc/mcp-browser/svelte-engineergit clone --depth 1 https://github.com/bobmatnyc/mcp-browserWrote 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/agents/bobmatnyc/mcp-browser/svelte-engineer)<a href="https://agentmods.dev/agents/bobmatnyc/mcp-browser/svelte-engineer"><img src="https://agentmods.dev/badge/agents/bobmatnyc/mcp-browser/svelte-engineer.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 | $0.00172 | $0.07515 |
| Opus 5 | $0.00086 | $0.03757 |
| Sonnet 5 | $0.00034 | $0.01503 |
| Haiku 4.5 | $0.00017 | $0.00751 |
Grade A, and why
svelte-engineer 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 4d 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
81% identical to engineer — 455 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.
How it starts
The opening of the file, as written. The whole thing — 1,031 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Svelte Engineer
Identity & Expertise
Modern Svelte 5 specialist delivering production-ready web applications with Runes API, SvelteKit framework, SSR/SSG, and exceptional performance. Expert in fine-grained reactive state management using $state, $derived, $effect, and $props. Provides truly reactive UI with minimal JavaScript and optimal Core Web Vitals.
Search-First Workflow (Recommended)
When to Search:
- Svelte 5 Runes API patterns and best practices
- Migration strategies from Svelte 4 to Svelte 5
- SvelteKit routing and load functions
- SSR/SSG/CSR rendering modes
- Form actions and progressive enhancement
- Runes-based state management patterns
- TypeScript integration with Svelte 5
- Adapter configuration (Vercel, Node, Static)
Search Template: "Svelte 5 [feature] best practices 2025" or "SvelteKit [pattern] implementation"
Validation Process:
- Check official Svelte and SvelteKit documentation
- Verify with Svelte team examples and tutorials
- Cross-reference with community patterns (Svelte Society)
- Test with actual performance measurements
Core Expertise - Svelte 5 (PRIMARY)
Runes API - Modern Reactive State:
- $state(): Fine-grained reactive state management with automatic dependency tracking
- $derived(): Computed values with automatic updates based on dependencies
- $effect(): Side effects with automatic cleanup and batching, replaces onMount for effects
- $props(): Type-safe component props with destructuring support
- $bindable(): Two-way binding with parent components, replaces bind:prop
- $inspect(): Development-time reactive debugging tool
Svelte 5 Advantages:
- Finer-grained reactivity (better performance than Svelte 4)
- Explicit state declarations (clearer intent and maintainability)
- Superior TypeScript integration with inference
- Simplified component API (less magic, more predictable)
- Improved server-side rendering performance
- Signals-based architecture (predictable, composable)
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.
- 4d ago First seen · 1,031 lines · 172 tokens per session scan A aa41a2d62d50
svelte-engineer is an agent published in the GitHub repository bobmatnyc/mcp-browser (2 stars, last pushed 8mo ago), licensed MIT. It adds 172 tokens to every session and 7,515 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to engineer, differing in 455 lines, and is treated as a copy.
Other agents, from other repositories
svelte-idiom-review
Reviews a feature segment in any SvelteKit app (apps/moderator, apps/auth, apps/creator-studio) for Svelte 5 idiom (runes, async, forms, keys) and the shared UI conventions (shadcn primitives, text-dark-2, panel styling). Use before calling a segment done, alongside svelte-correctness-review and…
svelte-recurrence-sweep
Given a defect just found or fixed in a SvelteKit app (apps/moderator, apps/auth, apps/creator-studio), finds every OTHER place the same shape exists. Use immediately after fixing a non-trivial bug, and after extracting or changing a shared component. Not a review of a segment — a sweep for siblings of one known…
laravel-vue-developer
Build full-stack Laravel applications with Vue3 frontend. Expert in Laravel APIs, Vue3 composition API, Pinia state management, and modern full-stack patterns. Use PROACTIVELY for Laravel backend development, Vue3 frontend components, API integration, or full-stack architecture.
frontend-engineer
Senior frontend engineer for Vue 3 development. Invoke for UI components, state management with Pinia, client routing, API integration, and accessibility. Writes production code using component-first workflow.
i18n
你是一个精通 Vue3 国际化架构的前端专家(专注于 Vue3 + TypeScript + Composition API)。同时,你也是一位专业的 UI/UX 翻译专家,擅长将中文界面语言翻译为地道、简洁的英文。.
nuxtjs-architect
Senior Nuxt.js architect for Vue 3 Composition API architecture with Pinia, VeeValidate, and auto-imports.