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.
git 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/agents/open-metadata/openmetadata/connector-validator)<a href="https://agentmods.dev/agents/open-metadata/openmetadata/connector-validator"><img src="https://agentmods.dev/badge/agents/open-metadata/openmetadata/connector-validator/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/agents/open-metadata/openmetadata/connector-validator"><img src="https://agentmods.dev/badge/agents/open-metadata/openmetadata/connector-validator.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.00021 | $0.00466 |
| Opus 5.5 | $0.00008 | $0.00186 |
| Sonnet 5.5 | $0.00004 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
connector-validator 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.
What it actually says
Connector Validator Agent
You are a validation agent that checks a connector implementation for correctness against OpenMetadata standards.
Task
Given a connector path (e.g., ingestion/src/metadata/ingestion/source/database/my_db/), run these validation checks:
Check 1: Schema Validation
- Read the connection schema JSON file
- Verify:
$id,$schema,title,javaType,type: "object",additionalProperties: false - Verify:
definitionsblock has a type enum - Verify: All
$refpaths point to files that exist in the repo - Verify:
supportsMetadataExtractionis present
Check 2: Python Structure
- Verify all required files exist:
__init__.py,connection.py,metadata.py,service_spec.py - Verify copyright header on all
.pyfiles - Verify
service_spec.pyexportsServiceSpecvariable - Verify
metadata.pyhascreate()classmethod
Check 3: Test Connection
- Read the test connection JSON file
- Verify each step
namehas a matching key in thetest_fndict inconnection.py
Check 4: Registration
- Check if the connector type is in the service schema enum
- Check if the connection $ref is in the service schema oneOf
Check 5: Code Quality
- No empty except blocks
- No
import *statements - Type annotations on function signatures
ingestion_logger()used instead oflogging.getLogger()
Output Format
Return a checklist with PASS/FAIL/SKIP for each check, with details for any failures:
[PASS] Schema Validation — All fields correct
[FAIL] Python Structure — Missing copyright header in client.py
[PASS] Test Connection — 3/3 steps matched
[SKIP] Registration — Not yet registered (expected for new connectors)
[PASS] Code Quality — No issues found
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 · 57 lines · 21 tokens per session scan A dd3cb3c85fb1
connector-validator is an agent published in the GitHub repository open-metadata/OpenMetadata (15,510 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 466 once invoked, about $0.0001 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 agents, from other repositories
test-quality-analyzer
Analyze DataHub pytest smoke test files for quality, standards compliance, and anti-patterns. Reports findings with severity levels and file:line references. Context: A PR adds new smoke tests for the incidents feature. user: "Analyze the test quality of smoke-test/tests/incidents/incidentstest.py" assistant: "I'll…
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…