Opik is an open-source platform for tracing, evaluating, and monitoring applications that use large language models, retrieval systems, or AI agents. Teams use it to inspect agent activity, manage prompts, run evaluations, and monitor these applications in production.
Borrowing it
Nothing to install: this file belongs to comet-ml/opik. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/comet-ml/opik/main/.agents/skills/playwright-pom-discovery/SKILL.mdgit clone --depth 1 https://github.com/comet-ml/opikWrote 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/comet-ml/opik/playwright-pom-discovery)<a href="https://agentmods.dev/skills/comet-ml/opik/playwright-pom-discovery"><img src="https://agentmods.dev/badge/skills/comet-ml/opik/playwright-pom-discovery.svg" alt="Measured on agentmods" height="20"></a>- Snyk pass
- 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.00112 | $0.04232 |
| Opus 5 | $0.00056 | $0.02116 |
| Sonnet 5 | $0.00022 | $0.00846 |
| Haiku 4.5 | $0.00011 | $0.00423 |
Grade A, and why
playwright-pom-discovery scanned grade A 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Run it locally with staging or local-dev creds, note the project name, then navigate the UI to that project's logs page in the next step. Tear it down by hand at the end of the discovery session (`backendClient.deletePro How it starts
The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright POM Discovery
This skill is the how of choosing selectors for a POM in the Opik E2E suite. You already know which POM you're building; this skill tells you how to figure out what's on the page, what selectors are stable, and how to verify your method actually works before checking it in.
Announce at start: "I'm using the playwright-pom-discovery skill to build the X page object."
When this skill applies
- You're touching anything under
tests_end_to_end/e2e/pom/. - You need to write a
data-testidselector, agetByRole, or any other Playwright locator targeting the live Opik UI. - You're adding a method to an existing POM that interacts with a new element you haven't seen before.
It does NOT apply to:
- Pure fixture work (no UI interaction).
- Matchers / type-only changes.
The procedure
digraph pom_discovery {
rankdir=TB;
"Identify target page + entity preconditions" [shape=box];
"Seed required state (project, dataset, trace, etc.)?" [shape=diamond];
"Create state via SDK / bridge before opening UI" [shape=box];
"Open page via browser_navigate (with auth)" [shape=box];
"browser_snapshot to get accessibility tree" [shape=box];
"browser_evaluate to enumerate data-testids" [shape=box];
"Pick selector preference (testid > role > label > css)" [shape=box];
"Write POM method" [shape=box];
"Verify via browser_generate_locator and test_run" [shape=box];
"Method works?" [shape=diamond];
"Selector unstable or missing?" [shape=diamond];
"Flag for FE data-testid addition" [shape=box];
"Commit POM method" [shape=box];
"Identify target page + entity preconditions" -> "Seed required state (project, dataset, trace, etc.)?";
"Seed required state (project, dataset, trace, etc.)?" -> "Create state via SDK / bridge before opening UI" [label="yes"];
"Create state via SDK / bridge before opening UI" -> "Open page via browser_navigate (with auth)";
"Seed required state (project, dataset, trace, etc.)?" -> "Open page via browser_navigate (with auth)" [label="no — stateless page"];
"Open page via browser_navigate (with auth)" -> "browser_snapshot to get accessibility tree";
"browser_snapshot to get accessibility tree" -> "browser_evaluate to enumerate data-testids";
"browser_evaluate to enumerate data-testids" -> "Pick selector preference (testid > role > label > css)";
"Pick selector preference (testid > role > label > css)" -> "Write POM method";
"Write POM method" -> "Verify via browser_generate_locator and test_run";
"Verify via browser_generate_locator and test_run" -> "Method works?";
"Method works?" -> "Commit POM method" [label="yes"];
"Method works?" -> "Selector unstable or missing?" [label="no"];
"Selector unstable or missing?" -> "Flag for FE data-testid addition" [label="yes"];
"Selector unstable or missing?" -> "browser_snapshot to get accessibility tree" [label="no, try different selector"];
"Flag for FE data-testid addition" -> "Pick selector preference (testid > role > label > css)";
}
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.
- 8d ago First seen · 282 lines · 112 tokens per session scan A 32431f5e4c8e
playwright-pom-discovery is a skill published in the GitHub repository comet-ml/opik (21,864 stars, last pushed today), licensed Apache-2.0. It adds 112 tokens to every session and 4,232 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.
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.
qa-systematic
Systematic web application QA testing with issue taxonomy, health scoring, and regression tracking. Triggers on: "QA this", "test the app", "smoke test", "run QA", "systematic test", "regression test", "full QA", "/qa-systematic".
control-ui
Drive and inspect a local web, IDE, or Electron UI with browser or CDP automation and evidence. Use for UI regressions, screenshots, accessibility snapshots, visual diffs, focus, keyboard, scrolling, resize, console, network, performance, or heap checks. Do not use for backend-only changes or for a screenshot without…
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
qa
Role: QA Lead Inputs: test-plan.md (from /plan-eng-review) + target URL Outputs: qa-report.md, regression tests in tests/ Audit actions: qa.started, qa.bugfound, qa.bugfixed, qa.testsgenerated.