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.
npx skills add open-metadata/OpenMetadata --skill writing-playwright-testsgit 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/skills/open-metadata/openmetadata/writing-playwright-tests)<a href="https://agentmods.dev/skills/open-metadata/openmetadata/writing-playwright-tests"><img src="https://agentmods.dev/badge/skills/open-metadata/openmetadata/writing-playwright-tests/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/writing-playwright-tests"><img src="https://agentmods.dev/badge/skills/open-metadata/openmetadata/writing-playwright-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Agent Snooping · line 9 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00038 | $0.00120 |
| Opus 5.5 | $0.00015 | $0.00048 |
| Sonnet 5.5 | $0.00008 | $0.00024 |
| Haiku 4.5 | $0.00004 | $0.00012 |
Grade A, and why
writing-playwright-tests 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 2mo 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
Writing Playwright Tests Skill
This skill has been merged into the playwright skill — see
skills/playwright/SKILL.md (section "Writing Playwright Tests") for authoring guidance, and its
"Mandatory verification" section for the required lint gate.
This file is kept only so existing references to writing-playwright-tests still resolve.
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.
- 2mo ago First seen · 13 lines · 38 tokens per session scan A 4cc4574d742f
writing-playwright-tests is a skill published in the GitHub repository open-metadata/OpenMetadata (15,615 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 120 once invoked, about $0.0002 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 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.
playground
Launches a local WordPress Playground site with The SEO Framework mounted, captures front-end SEO artifacts, and compares before/after plugin states. Use when testing regressions, reproducing bugs, changing meta/sitemap/robots/ schema/oEmbed/admin SEO output, checking WordPress version behavior, plugin conflicts, or…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.