OpenMetadata is an open platform that organizes information about data, including its meaning, ownership, quality, history, and relationships. It provides governed context for data users, AI assistants, and agents that need to discover and understand trustworthy data.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/open-metadata/OpenMetadatanpx agentmods add skills/open-metadata/openmetadata/ui-checkstyleWrote 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/open-metadata/openmetadata/ui-checkstyle)<a href="https://agentmods.dev/skills/open-metadata/openmetadata/ui-checkstyle"><img src="https://agentmods.dev/badge/skills/open-metadata/openmetadata/ui-checkstyle/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.
<a href="https://agentmods.dev/skills/open-metadata/openmetadata/ui-checkstyle"><img src="https://agentmods.dev/badge/skills/open-metadata/openmetadata/ui-checkstyle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00122 | $0.01754 |
| Opus 5.5 | $0.00049 | $0.00702 |
| Sonnet 5.5 | $0.00024 | $0.00351 |
| Haiku 4.5 | $0.00012 | $0.00175 |
Grade A, and why
ui-checkstyle 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 1mo 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Checkstyle / ESLint + Prettier + organize-imports
The UI Checkstyle GitHub workflow (.github/workflows/ui-checkstyle.yml) runs
a single checkstyle job (after check-changes + authorize gates) whose
steps gate six checks, each on only the files the PR changed:
- ESLint + Prettier + organize-imports on src
(
openmetadata-ui/src/main/resources/ui/src/...) - Licence header check
- i18n sync (
yarn i18nproduces no diff) - app-docs (
yarn generate:app-docsproduces no diff) - ESLint + Prettier + organize-imports on playwright (
.../ui/playwright/...) - ESLint + Prettier on core-components
(
openmetadata-ui-core-components/src/main/resources/ui/src/...)
Any failing step fails the required ui-checkstyle status check. Each lint
step reformats the changed files and fails if the reformat produces a diff — i.e.
the committed tree must already be formatted. This skill runs the same sequence
locally so CI never has to ask.
Note: there is one
checkstylejob with the steps above, not three separatelint-src/lint-playwright/lint-core-componentsjobs — those names are the internal step ids, and the workflow also gates licence/i18n/app-docs.
When to activate
- The user asks to "fix UI checkstyle", "fix UI lint", "run prettier", "run eslint", "fix the UI format", "apply UI format", or similar.
- CI reports a
UI Checkstylefailure (the summary comment lists the failing check and the modified files). - After you have finished authoring or editing any
.ts/.tsx/.js/.jsx/.jsonunder the three UI trees — before opening a PR or pushing a commit that touches UI.
Arguments
--src(default for files underopenmetadata-ui/.../ui/src/)--playwright(files under.../ui/playwright/)--core-components(files underopenmetadata-ui-core-components/...)--all— run all three areas--check— verify only: run the sequence in a dry-run pass and report which files are still dirty, without writing. Useful before push.
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.
- 1mo ago First seen · 154 lines · 122 tokens per session scan A ddabd9a46195
ui-checkstyle is a skill published in the GitHub repository open-metadata/OpenMetadata (15,525 stars, last pushed today), licensed Apache-2.0. It adds 122 tokens to every session and 1,754 once invoked, about $0.0005 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.
Other skills, from other repositories
tamagui-v6-config
Tamagui v6 theme system: the light/dark/accent/brand/inverse/level/active theme family, the background-active one-off key, and recipe-tree authoring with createV6Config. Use when choosing a theme for a surface, building a selected/emphasis state, or authoring a custom v6 colors pack.
tamagui-theme-generator
Generate custom Tamagui themes, color palettes, and preview URLs. Use when creating or refining a color scheme, authoring light/dark palettes with brand accents, or previewing generated themes in the browser.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
building-landing-home
Compose a product or documentation home page from the @lobehub/ui/awesome landing components: LandingHero, AgentSkillCard, LogoMarquee, LandingSection, BentoGrid/BentoCard, CodeShowcase, FeatureGrid, InstallBanner and FluidGradient. Covers page structure, the lobedocs homePage hook, router links, theming the accent…
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
byted-util-vite-react-tailwind
A setup guide for building frontend projects with Vite, React, Tailwind CSS, TypeScript, and Lucide icons.