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/pr-checklistWrote 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/pr-checklist)<a href="https://agentmods.dev/skills/open-metadata/openmetadata/pr-checklist"><img src="https://agentmods.dev/badge/skills/open-metadata/openmetadata/pr-checklist/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/pr-checklist"><img src="https://agentmods.dev/badge/skills/open-metadata/openmetadata/pr-checklist.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.00079 | $0.04301 |
| Opus 5.5 | $0.00032 | $0.01720 |
| Sonnet 5.5 | $0.00016 | $0.00860 |
| Haiku 4.5 | $0.00008 | $0.00430 |
Grade A, and why
pr-checklist 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 8d 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Checklist for OpenMetadata
Self-reviews the branch against REVIEW.md, walks through .github/pull_request_template.md section by section, gathers evidence, and produces a fully-filled PR description before creating the PR.
When to Use
- Before running
gh pr create - After finishing implementation, before requesting review
- Updating the description of an existing PR that's missing required sections
Usage
/pr-checklist # Walk template for current branch vs origin/main
/pr-checklist feature-branch # Same, for a different branch
/pr-checklist 12345 # Update description of an existing PR
Required Sections (from .github/pull_request_template.md)
Every PR must address each section below. Skip with an explicit "Not applicable — " rather than leaving blank.
- Linked issue —
Fixes #<issue-number>(GitHub auto-links). No issue → open one first. A test fix needs none (see Step 2). - Type of change — exactly one box checked.
- High-level design — required for large PRs (new features, refactors, breaking changes, >5 files); skip for small bug fixes.
- Tests — use cases covered, unit tests + coverage %, backend integration tests, ingestion integration tests, Playwright (UI) tests, manual test steps.
- UI screen recording — when creating a PR for a UI feature or feature task with UI impact, run the PR build in Docker with sample data and embed a verified GitHub-hosted video in the description. Use ui-pr-recording; other changes may explain N/A.
- Checklist — every box either checked or explicitly N/A.
Step-by-Step Workflow
Step 1 — Inspect the change
git status
git diff origin/main...HEAD --stat
git log origin/main..HEAD --oneline
Use the diff to classify the PR:
- Creating a PR for a UI feature or a feature task/subtask with UI impact → Docker run + recording + GitHub upload required. Use task/issue intent and the diff, not just paths or labels. Standalone fixes, refactors, styling, localization, docs, tests and backend-only changes may explain N/A.
- Touches
openmetadata-service/+ new/changed REST endpoints → backend integration tests required. - Touches Java, a JSON schema, an index mapping,
bootstrap/sql/, seed data or a pom → the impacted Java tests must pass locally (Step 3). PR CI runs only the unit tests. - Touches
ingestion/src/metadata/ingestion/source/→ ingestion tests required. - >5 files changed, or new feature / refactor / breaking change → high-level design required.
- Single-file fix with obvious scope → small change, design section can be
N/A.
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.
- 8d ago Changed · +34 lines · +6 tokens per session 531e2f8b3cef
- 14d ago Changed · +2 lines 0d3bd7fff58e
- 17d ago Changed · +41 lines cba226640f89
- 18d ago Changed · +4 lines 6fb41d455ed6
- 20d ago Changed · +45 lines a18c6ac62153
- 22d ago Changed · +3 lines 7481d6c6d0af
- 29d ago Changed · +8 lines 37e748cb8345
- 1mo ago First seen · 167 lines · 73 tokens per session scan A e61a03637c15
pr-checklist is a skill published in the GitHub repository open-metadata/OpenMetadata (15,601 stars, last pushed today), licensed Apache-2.0. It adds 79 tokens to every session and 4,301 once invoked, about $0.0003 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
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.
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…