DataHub is an open-source metadata platform that catalogs data assets so people can find, understand, govern, and monitor data across an organization’s data ecosystem. Data teams use it for data discovery, governance, observability, and answering questions about cataloged data with an analytics agent.
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/datahub-project/datahubWrote 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/rules/datahub-project/datahub/datahub-dev)<a href="https://agentmods.dev/rules/datahub-project/datahub/datahub-dev"><img src="https://agentmods.dev/badge/rules/datahub-project/datahub/datahub-dev/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/rules/datahub-project/datahub/datahub-dev"><img src="https://agentmods.dev/badge/rules/datahub-project/datahub/datahub-dev.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.00989 | $0.00989 |
| Opus 5.5 | $0.00396 | $0.00396 |
| Sonnet 5.5 | $0.00198 | $0.00198 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
datahub-dev 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DataHub Agent Workflow
datahub-dev CLI Tool
A stdlib-only Python CLI for agent-driven development. No venv needed — runs with system python3.
Always use the shell wrapper as the entry point:
scripts/dev/datahub-dev.sh <command>
Run scripts/dev/datahub-dev.sh --help to see all available subcommands (start, setup, frontend,
status, wait, rebuild, test, flag list/get, env, sync-flags, reset, nuke).
End-to-End Workflow
- Setup (once):
scripts/dev/datahub-dev.sh setup— installs Python dev environment (providesdatahubCLI). For frontend work, also runscripts/dev/datahub-dev.sh setup frontend. - Start:
scripts/dev/datahub-dev.sh start - Code: Make changes to Java/Python/frontend code
- Rebuild:
scripts/dev/datahub-dev.sh rebuild --wait - Test:
scripts/dev/datahub-dev.sh test <test-path> - Iterate: Repeat steps 2–4
Frontend hot-reload: Run scripts/dev/datahub-dev.sh frontend to start the React dev server with hot-reload (instead of rebuilding the frontend container).
Module-to-Container Mapping
| Source directory | Container |
|---|---|
metadata-service/ |
datahub-gms |
datahub-graphql-core/ |
datahub-gms |
metadata-io/ |
datahub-gms |
datahub-frontend/ |
datahub-frontend-react |
metadata-jobs/mce-consumer-job/ |
datahub-mce-consumer |
metadata-jobs/mae-consumer-job/ |
datahub-mae-consumer |
metadata-models/ |
All (triggers full rebuild + code generation) |
Environment Variables
Set any env var for DataHub containers via env set + env restart:
scripts/dev/datahub-dev.sh env set KEY=VALUE
scripts/dev/datahub-dev.sh env restart # required — changes take effect on restart
scripts/dev/datahub-dev.sh env list # show current vars and pending_restart status
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 Changed · +3 lines · +49 tokens per session 4a9cdf95873c
- 1mo ago First seen · 97 lines · 940 tokens per session scan A 6dba60e0c224
datahub-dev is a cursor rule published in the GitHub repository datahub-project/datahub (12,851 stars, last pushed today), licensed Apache-2.0. It adds 989 tokens to every session, about $0.0040 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 cursor rules, from other repositories
css
TSF stylesheet conventions, layout debugging, and minification.
docs
Readme wording constraints, WordPress readme format, changelog prose style, and public API naming requirements.
core
Repository coding standards and conventions for AI assistants.
clean-user-facing-text
Enforce invisible Unicode and steganography hygiene on user-facing text, manuscripts, and documentation.
bonnard-get-started
Guide a user through setting up their first semantic layer after bon init. Use when user says 'get started', 'what next', 'help me set up', or has just run bon init.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.