openui-component

A command for adding a new OpenUI component to a React component library. It creates a typed input schema with Zod and connects that schema to the component's renderer.

In plain words
What is it for?
Use it to create components for displaying data, accepting input, arranging content, or showing feedback in an OpenUI React library.
Why use it?
It gives AI-generated interface components a documented, validated set of inputs, reducing ambiguity about what each property should contain.

Command

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 commands/othmanadi/openui-forge/openui-component
Clone the repo
git clone --depth 1 https://github.com/OthmanAdi/openui-forge
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 478 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.00478
Opus 5 $0.00006 $0.00239
Sonnet 5 $0.00003 $0.00096
Haiku 4.5 $0.00001 $0.00048

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

Security

Grade A, and why

openui-component 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.

commands/openui-component.md · 53 lines

What it actually says

Create a new component and add it to the component library.

Step 1 — Gather requirements:

Ask the user:

  • What does this component display or do?
  • What props does it need? (or let the agent infer from the description)

Step 2 — Research patterns:

Read references/component-patterns.md for production examples that match the use case. Look for similar component types (data display, input, layout, feedback) and follow the same structural conventions.

Step 3 — Generate the component:

Use templates/component.tsx.template as the base structure. Create the component using defineComponent from @openuidev/react-lang:

import { defineComponent } from "@openuidev/react-lang";
import { z } from "zod";

export const ${NAME} = defineComponent({
  name: "${NAME}",
  description: "${DESCRIPTION}",
  props: z.object({
    // props here
  }),
  component: ({ props }) => (
    // JSX here
  ),
});

CRITICAL design rules (these directly affect LLM generation quality):

  • .describe() on EVERY Zod prop — this is the LLM's only documentation for what to put in each field
  • Flat schemas — avoid nesting deeper than 2 levels
  • Specific types — use z.enum(["sm", "md", "lg"]) over z.string() when values are constrained
  • Clear, unique names — the LLM picks components by name + description alone
  • Use ref from other DefinedComponents for nested component references
  • Keep the total library under 30 components — more = more prompt tokens = worse LLM output

Step 4 — Add to the library:

Find the existing createLibrary call in the project. Add the new component import and place it in the appropriate componentGroups group. If no suitable group exists, create one.

Step 5 — Regenerate the system prompt:

Remind the user to run /openui:prompt to regenerate the system prompt so the LLM knows about the new component. This step is mandatory — the LLM cannot use components it does not see in the system prompt.

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 · 53 lines · 13 tokens per session scan A a7d98e692262

Subscribe to this mod's changes

openui-component is a command published in the GitHub repository OthmanAdi/openui-forge (22 stars, last pushed 29d ago), licensed MIT. It adds 13 tokens to every session and 478 once invoked, about $0.0001 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.