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 agents/open-metadata/openmetadata/connector-validatorgit clone --depth 1 https://github.com/open-metadata/OpenMetadataWhat 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.00021 | $0.00466 |
| Opus 5 | $0.00010 | $0.00233 |
| Sonnet 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 2d 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.
- 2d 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,032 stars, last pushed 2d ago), licensed Apache-2.0. It adds 21 tokens to every session and 466 once invoked, about $0.0001 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 agents, from other repositories
test-quality-analyzer
Analyze DataHub smoke and integration 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…
report-generator
Use for generating formatted reports from database queries, creating data summaries, building dashboards, and exporting analysis results in various formats.
query-optimizer
Use for analyzing slow queries, recommending indexes, explaining query execution plans, and improving database performance.
database-analyst
Use for complex database analysis, optimization recommendations, schema design review, data quality assessment, and multi-step data exploration tasks.
qa
Use this agent when:\n\n1. A logical unit of work has been completed (feature implementation, bug fix, refactoring)\n2. Code changes are ready for review before committing or creating a pull request\n3. You need to verify that acceptance criteria and definition of done are met\n4. After making changes to test files to…
planner
Use this agent when the user presents a complex, multi-step task that requires clarification, decomposition, or planning before execution. This includes:\n\n \nContext: User requests a large feature implementation that spans multiple components.\nuser: "I need to add support for PostgreSQL as a metadata store…