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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/open-metadata/OpenMetadatanpx agentmods add skills/open-metadata/openmetadata/dev-setupWrote 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/dev-setup)<a href="https://agentmods.dev/skills/open-metadata/openmetadata/dev-setup"><img src="https://agentmods.dev/badge/skills/open-metadata/openmetadata/dev-setup/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/dev-setup"><img src="https://agentmods.dev/badge/skills/open-metadata/openmetadata/dev-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 152 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Rogue Agent · line 152 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00105 | $0.02164 |
| Opus 5.5 | $0.00042 | $0.00866 |
| Sonnet 5.5 | $0.00021 | $0.00433 |
| Haiku 4.5 | $0.00011 | $0.00216 |
Grade B, and why
dev-setup scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
`sudo systemctl enable --now docker` and `sudo usermod -aG docker $USER`, then log out and How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Environment Setup
Bring a checkout from "just cloned" to "can build the backend, the UI, and the ingestion framework" with one call.
When to Activate
- "set up my dev environment", "onboard me", "I just cloned this repo"
- "set up this worktree" (a Claude Code worktree does not inherit the main repo's venv)
- A build fails on a missing or wrong-version tool:
antlr4: command not found,class file has wrong version,Unsupported engine … node,ModuleNotFoundError: metadata.generated - "check my environment", "why doesn't
make generatework"
The One Call
./scripts/dev_setup.sh # or: make dev_setup
Everything is idempotent — re-running skips what is already correct. Useful flags
(pass through the Makefile as make dev_setup ARGS="--slim -y"):
| Flag | Effect |
|---|---|
--check |
Diagnose only, change nothing. Returns nonzero when issues are found. Always start here on an existing checkout. |
--slim |
Install ingestion[dev] instead of [all-dev-env]. Minutes instead of tens of minutes; omits most connector deps. Right choice unless the work touches a specific connector. |
-y |
Non-interactive (assumes yes for Homebrew/nvm/Docker prompts). |
--with-build |
Also runs mvn clean install -DskipTests -T 1C. |
--with-docker |
Also starts docker/development/docker-compose.yml. |
--skip-tools |
Verify system packages instead of installing them (no sudo/brew writes). |
--skip-python / --skip-ui / --skip-generate / --skip-precommit |
Skip that phase. |
--python <bin> |
Force the interpreter the venv is built from. |
Process
Step 1 — Diagnose before changing anything
./scripts/dev_setup.sh --check
Read the warnings. They name the exact missing piece; do not install anything the check reports as already present.
Step 2 — Choose the depth
- Backend/UI work only, or a new worktree →
./scripts/dev_setup.sh --slim -y - Connector or ingestion work →
./scripts/dev_setup.sh -y(full[all-dev-env]) - Ask the user before running the full install if they are on a metered/slow link — it downloads every connector's dependencies.
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 · 172 lines · 105 tokens per session scan B 5e9185199460
dev-setup is a skill published in the GitHub repository open-metadata/OpenMetadata (15,490 stars, last pushed today), licensed Apache-2.0. It adds 105 tokens to every session and 2,164 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
akf-trust-metadata
The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing.
conventional-commit-message
Generate high-quality Conventional Commit messages for repositories using conventional-changelog-conventionalcommits.
oss-fuzz
Run Tika's OSS-Fuzz Jazzer targets locally against a working-tree checkout — build the image, build fuzzers from local source, fuzz a target, run a corpus as a regression pass, reproduce a crash, and add seeds. Use for "fuzz the OneNote parser", "run OneNoteParserFuzzer against these files", "reproduce an OSS-Fuzz…
file-to-markdown
Turn almost any file into Markdown plus metadata — PDF, Office, HTML, email, archives, images, audio/video, 1000+ formats — powered by Apache Tika, either via the tika-app CLI (zero setup, one file) or a running tika-server (curl, warm process, many calls). Leads with rmeta (structured, embedded-item-aware output) as…
development
Ground rules for working in the Tika codebase — git policy, Maven wrapper/repo conventions, building and testing specific modules, code and test conventions, pre-commit checks. Load at session start for any Tika development task.