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 skills/yonatangross/orchestkit/json-render-catalognpx skills add yonatangross/orchestkit --skill json-render-cataloggit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/skills/yonatangross/orchestkit/json-render-catalog)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/json-render-catalog"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/json-render-catalog.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.00099 | $0.06509 |
| Opus 5 | $0.00049 | $0.03254 |
| Sonnet 5 | $0.00020 | $0.01302 |
| Haiku 4.5 | $0.00010 | $0.00651 |
Grade A, and why
json-render-catalog 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 yesterday.
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 — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.
json-render Component Catalogs
json-render (Vercel Labs, 12.9K stars, Apache-2.0) is a framework for AI-safe generative UI. AI generates flat-tree JSON (or YAML) specs constrained to a developer-defined catalog — the catalog is the contract between your design system and AI output. If a component or prop is not in the catalog, AI cannot generate it.
Storybook → catalog import (#1529, 2026-04)
When the project ships a Storybook setup, import the catalog from Storybook stories instead of hand-writing one. The bundled importer at scripts/storybook-to-catalog.mjs reads a @storybook/addon-mcp list-all-documentation manifest and emits a Zod-typed catalog.ts plus a components.tsx registry.
node "${CLAUDE_PLUGIN_ROOT}/skills/json-render-catalog/scripts/storybook-to-catalog.mjs" storybook-manifest.json \
--out src/genui/catalog.ts \
--components src/genui/components.tsx \
--project-root .
Storybook becomes the single source of truth — adding a story automatically expands the AI-allowed surface; removing one shrinks it. AI safety is enforced at import: callbacks, raw object props, and z.any() are dropped. Full mapping: references/storybook-import.md. Companion fixture for testing: references/storybook-fixture.json.
New in 2026-04 → 2026-08 (json-render 0.14 → 0.20)
- Named slots (0.20) —
UIElementgainsslots?: Record<string, string[]>, a catalog declares which it accepts viaslots: ["default", "header", "footer"], and a React registry component receives named content asslots?.headerwhilechildrenstays the default slot. Prefer this over encoding layout regions as separate sibling elements. - Nested repeats and item-scoped visibility (0.20) —
repeat.statePathaccepts an item-relative{"$item": "employees"}form (newRepeatStatePathtype plusresolveRepeatStatePath/resolveRepeatItemStatePath), and arepeatcombined withvisible: {"$item": "status", "eq": "todo"}on the same element now filters items instead of erroring.validateSpecgainsinvalid_visible,repeat_without_children,repeat_item_outside_scopeandrepeat_state_mismatchissue codes. - Custom directives API (0.19) —
@json-render/corenow shipsdefineDirective, letting you declare new JSON shapes (e.g.$format,$math) that resolve to computed values at render time. Directives compose by nesting and resolve inside-out. All four renderers (React, Vue, Svelte, Solid) have built-in directive resolution. This is the safe escape hatch for computed values without widening the catalog toz.any(). @json-render/directivespackage (0.19) — seven ready-made directives:$format(date / currency / number / percent viaIntl),$math(add, subtract, multiply, divide, mod, min, max, round, floor, ceil, abs),$concat,$count,$truncate,$pluralize,$join. PluscreateI18nDirectivefor$ttranslation keys with{{param}}interpolation, andstandardDirectivesfor one-line registration. Register once, use in any spec — AI no longer needs string-mangling or duplicated literals.- Devtools ecosystem (0.18) — five new packages:
@json-render/devtoolscore + framework adapters for React, Vue, Svelte, Solid. Inspector panel has six tabs (Spec, State, Actions, Stream, Catalog, Pick) with DOM element picking that maps back to spec keys. Tree-shakes tonullin production. Companion Next.js demo app shipped with AI-chat + catalog integration. Action observer infrastructure exposed for adapters to mirror events into the panel. - Zod 4 fix (0.18) —
formatZodTypenow correctly handlesz.record(),z.default(), andz.literal()(previously produced empty/wrong prompt output). - Three edit modes (0.14) —
patch(RFC 6902),merge(RFC 7396),diff(unified) for progressive AI refinements.buildEditUserPrompt()+diffToPatches()+deepMergeSpec()in@json-render/core. @json-render/yaml(0.14) — official YAML wire format + streaming parser;buildUserPrompt({ format: 'yaml' }).@json-render/ink(0.15) — render catalogs to terminal UIs (Ink-based, 20+ components) using the same spec.@json-render/next(0.16) — generate full Next.js apps (routes, layouts, SSR, metadata) from a single spec.@json-render/shadcn-svelte(0.16) — 36-component Svelte 5 + Tailwind mirror of the React shadcn catalog.- shadcn catalog at 36 components (was documented as 29 — the count was wrong even at 0.13). Use
@json-render/shadcnas-is, or spreadshadcnComponentDefinitionstogether with your own definitions. @json-render/react-three-fiberships 19 components (verified 2026-07-31 against the upstream skill; do not restate the roster here, see Upstream coverage).@json-render/mcp— upgrade plain MCP tool JSON into interactive iframes inside Claude/Cursor/ChatGPT conversations. See theork:mcp-visual-outputskill.- MCP multi-surface: same spec renders to React, PDF (
@json-render/react-pdf), email (@json-render/react-email), terminal (Ink), Next.js apps, and Remotion videos.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/ork-delta.md 2.9 KB
- references/package-ecosystem.md 3.6 KB
- references/storybook-fixture.json 2.6 KB
- references/storybook-import.md 6.2 KB
- rules/_sections.md 1.1 KB
- rules/_template.md 339 B
- rules/catalog-definition.md 3.8 KB
- rules/prop-constraints.md 3.4 KB
- rules/token-optimization.md 3.9 KB
- scripts/storybook-to-catalog.mjs 11 KB runs code
- test-cases.json 3.4 KB
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.
- yesterday First seen · 487 lines · 99 tokens per session scan A 8611f5db50f3
json-render-catalog is a skill published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 6,509 once invoked, about $0.0005 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 skills, from other repositories
web-design
UI review against Web Interface Guidelines. Use when asked to review UI, check accessibility, or audit design.
audit
Review past Claude Code sessions for PBR workflow compliance and UX quality.
shadcn-ui-flutter
A comprehensive Flutter UI library inspired by shadcn/ui. Provides high-quality, customizable, and accessible components including Buttons, Cards, Forms, and more. Use this skill when building Flutter UIs, implementing design systems, or needing specific component usage examples.
ui-design-source
Use this skill when the user provides Figma material, design-export files, screenshots of design tools, PDFs, JSON, existing HTML, or asks for design-to-HTML/code fidelity. It adapts OpenDesign/Figma handoff discipline for UIDesigner without requiring a live Figma runtime.
ux-design
Create comprehensive UX design with user flows, wireframes, and design systems.
launch-shadcn-registry
Launch and promote a custom shadcn/ui registry end-to-end: validate registry.json, prepare the official shadcn-ui/ui directory PR, community directory PRs (registry.directory, shadcntemplates, birobirobiro/awesome-shadcn-ui, bytefer/awesome-shadcn-ui), and draft social posts for Reddit r/shadcn, X, Dev.to, and Hacker…