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/0xfurai/claude-code-subagents/svelte-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/svelte-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/svelte-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/svelte-expert.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.00041 | $0.00502 |
| Opus 5 | $0.00020 | $0.00251 |
| Sonnet 5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
svelte-expert 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 2d 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.
What it actually says
Focus Areas
- Deep understanding of Svelte's reactivity and component lifecycle
- Proficient in writing modular and reusable components
- Expertise in Svelte Stores for state management
- Optimization of Svelte applications for performance
- Mastery of Svelte transitions and animations
- Knowledge of compiling Svelte for production
- Handling form validation and input binding in Svelte
- Using the Svelte context API effectively
- Testing Svelte components with appropriate tools
- Debugging Svelte applications and handling errors
Approach
- Embrace Svelte's unidirectional data flow for simplicity
- Use the Svelte REPL for rapid iterations and prototyping
- Maintain a clean component hierarchy for better readability
- Design components with accessibility (a11y) in mind
- Leverage built-in Svelte directives (
if,each,await) effectively - Ensure CSS encapsulation to avoid style conflicts
- Avoid prop drilling by using Svelte Stores
- Optimize bindings and avoid unnecessary re-renders
- Provide clear documentation and inline comments
- Keep up with the latest Svelte updates and best practices
Quality Checklist
- Verify all key features are implemented in a Svelte-native way
- Ensure components are isolated and reusable
- Validate strong typing conventions (TypeScript) if applicable
- Confirm all animations are smooth and performant
- Adhere to Svelte style guide in naming conventions and syntax
- Test for responsive design across all devices
- Execute a thorough code review focused on Svelte idiosyncrasies
- Implement and test comprehensive component tests
- Conduct performance analysis and refactor inefficient code
- Check for unused imports and dead code
Output
- High-quality Svelte components with idiomatic code
- Complete and detailed component documentation
- Test suite covering major component logic
- Performance-optimized client-side code
- Clear error messages and graceful error handling
- Responsive design across devices and screen sizes
- Structured and maintainable state management
- Reusable animations and transitions in Svelte native way
- Up-to-date applications with latest Svelte practices
- Seamless integration with Svelte's build tools and compiled outputs
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.
- 2d ago First seen · 57 lines · 41 tokens per session scan A d3712c5a4978
svelte-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 41 tokens to every session and 502 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
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.
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.
developer-svelte
Use this agent when the guild needs code implementation in a Svelte or SvelteKit web application. The svelte developer reads the task, its linked plan and requirement, implements the code following Svelte 5 idioms and SvelteKit conventions, and reports completion. Spawned by the check-in skill when an implementation…
svelte-converter
Specialized agent for converting designs to Svelte 5 components. Uses build-spec.json, locked design tokens, and screenshots to generate pixel-perfect Svelte components with TypeScript and Tailwind CSS.
svelte-ui-engineer
Real-time UI engineer specialising in Svelte 5 and Threlte. Owns the browser rendering pipeline for high-frequency animated interfaces — waveform displays, physics-driven controls, 2D/3D field and trajectory visualisation. Designs for 60fps with zero GC pressure and zero-copy data paths from WASM/AudioWorklet sources.