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/playwright-validationWrote 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/playwright-validation)<a href="https://agentmods.dev/skills/open-metadata/openmetadata/playwright-validation"><img src="https://agentmods.dev/badge/skills/open-metadata/openmetadata/playwright-validation/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/playwright-validation"><img src="https://agentmods.dev/badge/skills/open-metadata/openmetadata/playwright-validation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.01380 |
| Opus 5.5 | $0.00015 | $0.00552 |
| Sonnet 5.5 | $0.00007 | $0.00276 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade A, and why
playwright-validation 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Validation Skill
This skill guides you through validating UI changes and ensuring comprehensive Playwright E2E test coverage.
When to Use
- After completing UI feature development
- Before creating a PR for UI changes
- When reviewing UI-related branches
- To verify existing Playwright tests cover all scenarios
Workflow
Phase 1: Review Branch Changes
-
Identify changed files vs main:
git diff main --stat git diff main --name-only | grep -E "\.(tsx?|less|css|scss)$" -
Focus on UI component changes:
git diff main -- "openmetadata-ui/src/main/resources/ui/src/components/**" --stat -
Check for existing Playwright tests:
git diff main --name-only | grep -E "playwright.*\.spec\.ts$" -
Read the changed component files to understand the UI modifications
Phase 2: Review Existing Playwright Tests
-
Locate relevant test files:
- Check
playwright/e2e/Pages/for page-level tests - Check
playwright/e2e/Features/for feature-specific tests - Use Glob/Grep to find tests related to the feature
- Check
-
Analyze test coverage:
- Read the existing test file(s)
- Identify the test scenarios already covered
- Note any gaps in coverage based on the UI changes
-
Review test utilities:
- Check
playwright/utils/for helper functions - Check
playwright/support/for entity classes and fixtures
- Check
Phase 3: Validate with Playwright MCP
-
Start the browser and navigate:
mcp__playwright__browser_navigate to http://localhost:8585 -
Authenticate if needed:
- Use
mcp__playwright__browser_fill_formfor login - Default admin:
[email protected]/admin
- Use
-
Navigate to the feature area:
- Use
mcp__playwright__browser_clickfor navigation - Use
mcp__playwright__browser_snapshotto inspect page state
- Use
-
Validate UI behavior:
- Test the main user flows
- Verify visual elements (icons, badges, labels)
- Check interactive elements (buttons, dropdowns, forms)
- Verify state changes and API calls
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 · 179 lines · 37 tokens per session scan A 5d1f19151a1e
playwright-validation is a skill published in the GitHub repository open-metadata/OpenMetadata (15,500 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 1,380 once invoked, about $0.0001 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
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
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.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.