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
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 skills add open-metadata/OpenMetadata --skill java-affected-testsgit 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/java-affected-tests)<a href="https://agentmods.dev/skills/open-metadata/openmetadata/java-affected-tests"><img src="https://agentmods.dev/badge/skills/open-metadata/openmetadata/java-affected-tests/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/java-affected-tests"><img src="https://agentmods.dev/badge/skills/open-metadata/openmetadata/java-affected-tests.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00120 | $0.02545 |
| Opus 5.5 | $0.00048 | $0.01018 |
| Sonnet 5.5 | $0.00024 | $0.00509 |
| Haiku 4.5 | $0.00012 | $0.00254 |
Grade A, and why
java-affected-tests 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 yesterday.
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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java tests to run before a PR
| Suite | PR checks | Merge queue | Nightly | You, before the PR |
|---|---|---|---|---|
| Unit tests | full | full | — | impacted classes |
Integration tests (openmetadata-integration-tests) |
skipped | full, every lane and engine | — | impacted classes |
search-it (tests/search/*IT) |
— | — | openmetadata-nightly | impacted classes |
JavaUIIT (*UIIT), scale-it |
— | — | openmetadata-nightly | reported, not run |
The merge queue is the first CI run of the ITs. An IT failure there ejects the PR and re-tests every PR queued behind it. Search-indexing changes have no pre-merge CI at all, so your run is their only check before merge. Run what the planner selects, every time.
1. Preconditions
git fetch origin main, so the diff base is current. The planner diffsorigin/main...HEADplus uncommitted and untracked files.- Docker running, with no other Testcontainers stack up:
docker ps --filter label=org.testcontainers=true. Another checkout's ITs plus yours rarely fit in Docker's memory. Wait for them; don't stop them. - JDK 21. No
mvn installneeded: every command builds the modules under test with-am.
2. Plan
make java_affected # what runs, why, and the exact commands
| Planner output | What to do |
|---|---|
No Java tests are impacted or No impacted Java test runs locally |
Put the NOT NEEDED block in the PR (make java_affected_run writes it and names any nightly-only tests) |
[unit] … FULL suite |
Expected for poms and widely used classes |
[integration] FULL suite |
Run it locally, or in CI on your branch and record the run with --ci-run (section 3) |
[integration] Class lane engine <- reason |
Run them all; the reason names the area, entity, reference or caller |
Impacted, but not run locally |
List them in the PR with where they run (nightly, external cluster); don't run |
Changed classes no unit test references |
Add a unit test (see test-enforcement), or say in the PR why none applies |
Impact-map gaps |
Add the file's directory to the area that owns that code in .github/java-tests/impact-map.json, in this PR, then re-plan. Until then the full suite runs |
Fix .github/java-tests/impact-map.json in this branch before you raise the PR |
Do what each line says: add the named glob to an area's sources, a pattern for the new IT to its tests, or remove a pattern your deletions emptied. git push and gh pr create stay blocked until it's clean (rule java-impact-map.md) |
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.
- yesterday Changed aba128189edf
- 2d ago Changed · +4 lines 4600b3fdc3b3
- 6d ago Changed · +1 lines 20389554824a
- 7d ago Changed · +4 lines c0986f9d5841
- 8d ago First seen · 153 lines · 120 tokens per session scan A 014f8a3eeda4
java-affected-tests is a skill published in the GitHub repository open-metadata/OpenMetadata (15,490 stars, last pushed today), licensed Apache-2.0. It adds 120 tokens to every session and 2,545 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-10-08.
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.
java-unit-test
A code-generation guide for Java unit tests in Spring Boot projects. Unit tests check one small piece of code in isolation; Spring Boot is a Java framework for building web applications and services.
testng-skill
Generates TestNG tests in Java with groups, data providers, parallel execution, XML suite configuration, and listeners. Use when user mentions "TestNG", "@DataProvider", "testng.xml", "groups". Triggers on: "TestNG", "@DataProvider", "testng.xml", "TestNG suite", "parallel tests Java".
JUnit 5 Testing
Production-grade Java unit and integration testing with JUnit 5 covering assertions, parameterized tests, lifecycle hooks, Mockito mocking, nested tests, and extensions.
test-quality
Write high-quality JUnit 5 tests with AssertJ assertions. Use when user says "add tests", "write tests", "improve test coverage", or when reviewing/creating test classes for Java code.
111-java-maven-dependencies
Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a…