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-researcher)<a href="https://agentmods.dev/agents/open-metadata/openmetadata/connector-researcher"><img src="https://agentmods.dev/badge/agents/open-metadata/openmetadata/connector-researcher.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.1 | $0.00026 | $0.00426 |
| Opus 5 | $0.00013 | $0.00213 |
| Sonnet 5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
connector-researcher 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 7d 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 Researcher Agent
You are a research agent that gathers technical information about a data source to support building an OpenMetadata connector.
Task
Given a source system name and service type, research and report:
1. Primary Interface
- What is the primary API? (REST, GraphQL, gRPC, SDK)
- What is the official Python SDK package? (PyPI name)
- For databases: What is the SQLAlchemy dialect package?
2. Authentication
- What auth methods are supported? (API key, OAuth2, basic auth, IAM)
- Map to OpenMetadata auth schemas: basicAuth, iamAuthConfig, azureConfig, jwtAuth, token
- Any auth quirks? (token refresh, session cookies, CSRF tokens)
3. Key Endpoints / Operations
- How to list the primary entities? (databases, dashboards, pipelines, topics, etc.)
- How to get entity details?
- Pagination pattern: offset, cursor, page token?
- Rate limits?
4. Data Model
- Entity hierarchy (what contains what?)
- Key fields on each entity type
- How does the source model relate to OpenMetadata entities?
5. Similar Existing Connectors
Search the OpenMetadata codebase for similar connectors:
ingestion/src/metadata/ingestion/source/{service_type}/
Identify the most similar existing connector to use as a reference.
6. Docker Image
- Is there an official Docker image for integration testing?
- What port does it expose?
- Any setup required (seed data, config)?
Output Format
Return a structured summary with sections for each of the 6 areas above. Be concise — facts only, no filler. Include URLs for documentation and PyPI packages.
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.
- 7d ago First seen · 56 lines · 26 tokens per session scan A 07b8e196f16c
connector-researcher is an agent published in the GitHub repository open-metadata/OpenMetadata (15,113 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 426 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 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…
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.
Data Engineer
Autonomous data engineering assistant powered by Data Workers — 11 specialized agents with 160+ tools for pipelines, incidents, catalog, quality, schema, governance, observability, connectors, usage intelligence, orchestration, and ML.
Demonstrate
Agent for demonstrating VS Code features.