svelte

svelte is a skill for Claude Code, Codex from vercel-labs/json-render. It costs 49 tokens per session (1,814 once invoked), scanned A, original, Apache-2.0.

A Svelte 5 renderer that turns json-render JSON specifications into Svelte component trees. json-render is a system for describing user interfaces as JSON rather than hand-writing every screen.

In plain words
What is it for?
It is for Svelte applications that render AI-generated or other JSON-based UI specifications. It helps register components such as cards and buttons, define their properties, and render them from a specification.
Why use it?
It lets an application render JSON-defined interfaces with its own Svelte components. A component catalog describes which components and properties the renderer may use.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

Good fit It is for Svelte applications that render AI-generated or other JSON-based UI specifications. It helps register components such as cards and buttons, define their properties, and render them from a specification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vercel-labs/json-render/svelte
About the project

json-render is a framework where AI produces user interfaces as structured JSON constrained by a developer-defined component catalogue. It is for building dynamic interfaces from natural-language prompts across web and mobile frameworks.

vercel-labs/json-render · 19,433 stars · on GitHub · json-render.dev

Install

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.

Any agent
npx skills add vercel-labs/json-render --skill svelte
Clone the repo
git clone --depth 1 https://github.com/vercel-labs/json-render

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/vercel-labs/json-render/svelte/github.svg)](https://agentmods.dev/skills/vercel-labs/json-render/svelte)
Your own site
<a href="https://agentmods.dev/skills/vercel-labs/json-render/svelte"><img src="https://agentmods.dev/badge/skills/vercel-labs/json-render/svelte/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.

agentmods 80×15 button for svelte

Your own site · 80×15
<a href="https://agentmods.dev/skills/vercel-labs/json-render/svelte"><img src="https://agentmods.dev/badge/skills/vercel-labs/json-render/svelte.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,814 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 14 Sept 2026
  • Snyk pass 14 Sept 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Prompt Injection · line 71
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
How audits are shown
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.00049 $0.01814
Opus 5.5 $0.00020 $0.00726
Sonnet 5.5 $0.00010 $0.00363
Haiku 4.5 $0.00005 $0.00181

Measured 2mo ago against content hash 03e6e301b519, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

svelte 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 2mo 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.

skills/svelte/SKILL.md · 287 lines

How it starts

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

@json-render/svelte

Svelte 5 renderer that converts json-render specs into Svelte component trees.

Quick Start

<script lang="ts">
  import { Renderer, JsonUIProvider } from "@json-render/svelte";
  import type { Spec } from "@json-render/svelte";
  import Card from "./components/Card.svelte";
  import Button from "./components/Button.svelte";

  interface Props {
    spec: Spec | null;
  }

  let { spec }: Props = $props();
  const registry = { Card, Button };
</script>

<JsonUIProvider>
  <Renderer {spec} {registry} />
</JsonUIProvider>

Creating a Catalog

import { defineCatalog } from "@json-render/core";
import { schema } from "@json-render/svelte";
import { z } from "zod";

export const catalog = defineCatalog(schema, {
  components: {
    Button: {
      props: z.object({
        label: z.string(),
        variant: z.enum(["primary", "secondary"]).nullable(),
      }),
      description: "Clickable button",
    },
    Card: {
      props: z.object({ title: z.string() }),
      description: "Card container with title",
    },
  },
});

Defining Components

Components should accept BaseComponentProps<TProps>:

interface BaseComponentProps<TProps> {
  props: TProps; // Resolved props for this component
  children?: Snippet; // Child elements (use {@render children()})
  emit: (event: string) => void; // Fire a named event
  bindings?: Record<string, string>; // Map of prop names to state paths (for $bindState)
  loading?: boolean; // True while spec is streaming
}
<!-- Button.svelte -->
<script lang="ts">
  import type { BaseComponentProps } from "@json-render/svelte";

  interface Props extends BaseComponentProps<{ label: string; variant?: string }> {}
  let { props, emit }: Props = $props();
</script>

<button class={props.variant} onclick={() => emit("press")}>
  {props.label}
</button>
<!-- Card.svelte -->
<script lang="ts">
  import type { Snippet } from "svelte";
  import type { BaseComponentProps } from "@json-render/svelte";

  interface Props extends BaseComponentProps<{ title: string }> {
    children?: Snippet;
  }

  let { props, children }: Props = $props();
</script>

<div class="card">
  <h2>{props.title}</h2>
  {#if children}
    {@render children()}
  {/if}
</div>

Read the full file on GitHub · 287 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. 2mo ago First seen · 287 lines · 49 tokens per session scan A 03e6e301b519

Subscribe to this mod's changes

svelte is a skill published in the GitHub repository vercel-labs/json-render (19,433 stars, last pushed yesterday), licensed Apache-2.0. It adds 49 tokens to every session and 1,814 once invoked, about $0.0002 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-08-30.

Related

svelte compared with skills from other repositories

svelte next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
sveltevercel-labs/json-renderSkill19kyesterdayApache-2.0A49Claude Code, Codex
add-localizationmicrosoft/power-platform-skillsSkill1.1ktodayMITA69Claude Code
vue-router-best-practicesvuejs-ai/skillsSkill3.3k16d agoMITA25Claude Code, Codex
moai-domain-uiuxmodu-ai/moai-adkSkill1.3ktodayApache-2.0A49Claude Code
frontend-conventionsfpindej/netrockSkill2355d agoMITA27Claude Code
native-to-weapp-vite-wevu-migrationweapp-vite/weapp-viteSkill519todayMITA106Codex
weapp-vite-vue-sfc-best-practicesweapp-vite/weapp-viteSkill519todayMITA107Codex