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/pr-checklistnpx skills add open-metadata/OpenMetadata --skill pr-checklistgit 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/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.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.00073 | $0.01525 |
| Opus 5 | $0.00036 | $0.00763 |
| Sonnet 5 | $0.00015 | $0.00305 |
| Haiku 4.5 | $0.00007 | $0.00153 |
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 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Checklist for OpenMetadata
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. - 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 / screenshots — required for any UI change.
- 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:
- Touches
openmetadata-ui/src/main/resources/ui/→ UI change (recording required). - Touches
openmetadata-service/+ new/changed REST endpoints → backend integration tests required. - 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.
- 4d 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,059 stars, last pushed yesterday), licensed Apache-2.0. It adds 73 tokens to every session and 1,525 once invoked, about $0.0004 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.
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".