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/open-metadata/openmetadata/ui-core-componentsnpx skills add open-metadata/OpenMetadata --skill ui-core-componentsgit clone --depth 1 https://github.com/open-metadata/OpenMetadataWhat 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.00119 | $0.01728 |
| Opus 5 | $0.00060 | $0.00864 |
| Sonnet 5 | $0.00024 | $0.00346 |
| Haiku 4.5 | $0.00012 | $0.00173 |
Grade A, and why
ui-core-components 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Core Components
@openmetadata/ui-core-components ships layout primitives that replace common
<div className="tw:flex ..."> / <div className="tw:grid ..."> patterns.
383+ files in openmetadata-ui already import from this package. Baseline
testing shows agents default to raw div + Tailwind for layout unless told
these exist — check this table before writing layout markup.
When to use a primitive vs. a raw div
Only layout container divs (the ones whose className is mostly
flex/grid/gap/items-*/justify-*/border-as-separator) go through a
primitive. Leave alone: single non-layout divs, text wrappers, spans, icon
wrappers, and anything built from antd/other external library form components — this is not a
"replace every div" rule.
Quick reference
| Raw pattern | Use instead |
|---|---|
<div className="tw:flex ..."> (row) |
<Box> |
<div className="tw:flex tw:flex-col ..."> |
<Box direction="col"> |
<div className="tw:grid ..."> with column spans |
<Grid> + <Grid.Item span={n} start={n}> |
| Bordered container with a title/actions row, body, footer row | <Card> + <Card.Header title=.. extra=..> / <Card.Content> / <Card.Footer> |
<hr> or <div className="tw:h-px tw:bg-..."> separator, optionally with a centered label |
<Divider> (orientation, label, labelAlign) |
Import from the package root:
import { Box, Card, Divider, Grid } from '@openmetadata/ui-core-components';
Box
Box renders a flex (or inline-flex) div. Layout goes through props, not
className:
direction:'row' | 'col' | 'row-reverse' | 'col-reverse'(default row)align:'start' | 'center' | 'end' | 'stretch' | 'baseline'justify:'start' | 'center' | 'end' | 'between' | 'around' | 'evenly'wrap:'wrap' | 'nowrap' | 'wrap-reverse'gap/rowGap/colGap: Tailwind spacing scale (0–12,14,16...96), not raw pxinline: boolean —inline-flexinstead offlex
className is still accepted for one-off overrides (margins, borders,
backgrounds) — use it for what isn't a layout-direction/gap concern, not to
re-add tw:flex.
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.
- 3d ago First seen · 156 lines · 119 tokens per session scan A bdb5dfc3366e
ui-core-components is a skill published in the GitHub repository open-metadata/OpenMetadata (15,059 stars, last pushed yesterday), licensed Apache-2.0. It adds 119 tokens to every session and 1,728 once invoked, about $0.0006 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.
Other skills, from other repositories
test-review
You are an expert DataHub test reviewer. Your role is to evaluate smoke tests and integration tests against established testing standards, identify issues, and provide actionable feedback.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
row-selection
Maintain rowSelection ID state with stable getRowId, single, multi, subrow, and Shift-range rules, selected row models, handler anchors, and manual-pagination semantics. Load when implementing getToggleSelectedHandler, enableRowRangeSelection, selectChildren, deselectParents, or selected IDs that outlive loaded Row…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.