vercel-composition-patterns

Guidelines for designing reusable React components and their interfaces, including compound components, render props, and shared context.

In plain words
What is it for?
They are for refactoring React components, building flexible libraries, designing reusable interfaces, and applying React 19 patterns.
Why use it?
They help reduce tangled components with too many on/off properties and make component libraries easier to extend.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/langfuse/langfuse/vercel-composition-patterns
Any agent
npx skills add langfuse/langfuse --skill vercel-composition-patterns
Clone the repo
git clone --depth 1 https://github.com/langfuse/langfuse

Made for: Claude Code, Codex.

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 626 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00058 $0.00626
Opus 5 $0.00029 $0.00313
Sonnet 5 $0.00012 $0.00125
Haiku 4.5 $0.00006 $0.00063

Measured 2d ago against content hash e38e0eaa6093, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vercel-composition-patterns 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.

web/.agents/skills/vercel-composition-patterns/SKILL.md · 90 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 90 lines · 58 tokens per session scan A e38e0eaa6093

Subscribe to this mod's changes

vercel-composition-patterns is a skill published in the GitHub repository langfuse/langfuse (33,936 stars, last pushed 2d ago), with no licence file. It adds 58 tokens to every session and 626 once invoked, about $0.0003 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-08-30.

Related

Other skills, from other repositories

create-atomic-tool

Build a BaseTool[InSchema, OutSchema] subclass — input/output schemas, BaseToolConfig, run() (and optional runasync()), env-driven secrets, typed failure outputs. Use when the user asks to "add a tool", "create a tool", "wrap an API as a tool", "build a BaseTool", "make a calculator/search/weather tool", or runs…

Eigenwise/atomic-agents · 99 tokens

framework

Guide for the Atomic Agents Python framework — schemas, agents, tools, context providers, prompts, orchestration, and provider configuration. Use when code imports from atomicagents, defines an AtomicAgent, BaseTool, or BaseIOSchema, or the user asks about multi-agent orchestration or LLM-provider wiring in an…

Eigenwise/atomic-agents · 74 tokens

create-atomic-agent

Build and wire an AtomicAgent[InSchema, OutSchema] — schemas, AgentConfig, SystemPromptGenerator, provider client, history, hooks, optional context providers. Use when the user asks to "create an agent", "add another agent", "build an AtomicAgent", "wire up an agent", "make a planner/router/extractor agent", or runs…

Eigenwise/atomic-agents · 93 tokens

create-atomic-context-provider

Build a BaseDynamicContextProvider that injects a named, titled block into an agent's system prompt at every run() — current time, user identity, retrieved RAG docs, session state, cached DB schema. Use when the user asks to "add a context provider", "inject X into the prompt", "give the agent dynamic context", "wire…

Eigenwise/atomic-agents · 106 tokens

create-atomic-schema

Design and write a BaseIOSchema input/output pair for an Atomic Agents agent or tool — docstrings, field descriptions, validators, error variants. Use when the user asks to "create a schema", "design the input/output schema", "define an IOSchema", "write a BaseIOSchema", "model the agent's output", or runs…

Eigenwise/atomic-agents · 89 tokens

new-app

Scaffold a new Atomic Agents project from scratch — create the directory, pyproject.toml, env file, first agent, and a runnable entry point. Use when the user asks to start a new atomic-agents project from scratch, says "scaffold" / "new project" / "start from zero", or runs /atomic-agents:new-app.

Eigenwise/atomic-agents · 76 tokens