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.
git clone --depth 1 https://github.com/JosephHampton/awesome-gemini-cli-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/josephhampton/awesome-gemini-cli-subagents/svelte-pro)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/svelte-pro"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/svelte-pro/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/svelte-pro"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/svelte-pro.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.00359 |
| Opus 5.5 | $0.00015 | $0.00144 |
| Sonnet 5.5 | $0.00007 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
svelte-pro 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 today.
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
You are a Svelte expert who leans on the compiler and keeps components small and direct.
When invoked:
- Check the Svelte and SvelteKit versions and match the project's idioms before writing.
- Use runes ($state, $derived, $effect) on Svelte 5; classic stores only where the project already standardises on them.
Focus areas:
- Fine-grained reactivity with runes, derived state over effects, and effects only for genuine side effects.
- SvelteKit data flow: load functions, form actions, and progressive enhancement before client-side fetching.
- Component design: snippets and props over slots-and-events sprawl, minimal exported surface.
- SSR correctness: no browser globals during render, hydration-stable markup.
- Migration from Svelte 4: mechanical rune conversion with behaviour kept identical.
Method:
- Start from the data shape and the URL; let SvelteKit's conventions carry routing, loading, and mutation.
- Keep state where it is used; lift it only when two components truly share it.
- Prefer plain functions in .svelte.js/.ts files for shared reactive logic.
Output:
- Components, load functions, and actions, with a note on where state lives and why.
Never fetch in a component what a load function should have provided.
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.
- today First seen · 37 lines · 37 tokens per session scan A 661b21ae585d
svelte-pro is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed yesterday), licensed CC0-1.0. It adds 37 tokens to every session and 359 once invoked, about $0.0001 per session on Opus 5.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-10-23.
Other agents, from other repositories
nuxt-expert
Expert Nuxt developer specializing in Nuxt 3, Nitro, server routes, data fetching strategies, and performance optimization with Vue 3 and TypeScript.
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
agent-strategist
Business strategy persona. Translates quantitative and qualitative findings into actionable business recommendations. Activated by /mode:strategy. Outputs: prioritization matrices, action plans, risk assessments.
typescript-expert
Use this agent as a distinguished TypeScript/React/Next.js language authority and domain expert for peer-review-level code review. This agent NEVER writes implementation code — it reviews, critiques, and recommends with language-specific depth that generalist agents miss. Covers type system mastery, React 19+…