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-checkstylenpx skills add open-metadata/OpenMetadata --skill ui-checkstylegit clone --depth 1 https://github.com/open-metadata/OpenMetadataWrote 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.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.00122 | $0.01754 |
| Opus 5 | $0.00061 | $0.00877 |
| Sonnet 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 4d 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.
- 4d 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,098 stars, last pushed today), licensed Apache-2.0. It adds 122 tokens to every session and 1,754 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 pytest smoke tests against established testing standards, identify issues, and provide actionable feedback.
oss-fuzz
Run Tika's OSS-Fuzz Jazzer targets locally against a working-tree checkout — build the image, build fuzzers from local source, fuzz a target, run a corpus as a regression pass, reproduce a crash, and add seeds. Use for "fuzz the OneNote parser", "run OneNoteParserFuzzer against these files", "reproduce an OSS-Fuzz…
update-site-for-release
Update/publish the Apache Tika website (tika-site SVN repo) for a release — step 17 of the Release Process. Handles the 4.x track (Changes page + aggregate javadoc + Antora docs branch) vs the 3.x maintenance track (full per-version apt docs + javadoc). Use for "update the site", "publish the site for X.Y.Z", "the…
file-to-markdown
Turn almost any file into Markdown plus metadata — PDF, Office, HTML, email, archives, images, audio/video, 1000+ formats — powered by Apache Tika, either via the tika-app CLI (zero setup, one file) or a running tika-server (curl, warm process, many calls). Leads with rmeta (structured, embedded-item-aware output) as…
development
Ground rules for working in the Tika codebase — git policy, Maven wrapper/repo conventions, building and testing specific modules, code and test conventions, pre-commit checks. Load at session start for any Tika development task.
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".