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/debugging-e2e-tests/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/debugging-e2e-tests)<a href="https://agentmods.dev/skills/comet-ml/opik/debugging-e2e-tests"><img src="https://agentmods.dev/badge/skills/comet-ml/opik/debugging-e2e-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/comet-ml/opik/debugging-e2e-tests"><img src="https://agentmods.dev/badge/skills/comet-ml/opik/debugging-e2e-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- 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 MCP Rug Pull · line 30 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 63 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00122 | $0.01860 |
| Opus 5.5 | $0.00049 | $0.00744 |
| Sonnet 5.5 | $0.00024 | $0.00372 |
| Haiku 4.5 | $0.00012 | $0.00186 |
Grade A, and why
debugging-e2e-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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging E2E Tests
This skill investigates a failed test in the Opik E2E suite (tests_end_to_end/e2e/). You give it a failure from wherever you noticed it; it gathers the evidence, decides whether it's a real regression or a flake, and proposes a fix.
Announce at start: "I'm using the debugging-e2e-tests skill to investigate X."
What this does — and doesn't
- It diagnoses and proposes, grounded in cited evidence (the trace, the error, the history). It is read-only: it does not edit tests, and it does not re-run the suite as part of investigating.
- To apply a proposed fix, hand off to the
writing-e2e-testsskill (or just say "apply it") — that's a separate, deliberate act with its own run-until-green loop.
Where the evidence lives
- Local run — traces under
tests_end_to_end/e2e/test-results/(retained on failure), Allure results underallure-results/. - CI run — the suite uploads three artifacts per run (7-day retention):
test-results-v2(Playwright traces + videos),playwright-report-v2(the HTML report),allure-results-v2. Download withgh run download <run-id> -n test-results-v2 -D <dir>. - Allure TestOps (
comet.testops.cloud, project id1) — results stream live during CI. Launches are namedOpik v2 … <tier> - <run_id>(the trailing number is the GitHub Actions run id; the env segment varies —E2E,Post-Merge,Local,staging,production).
Tooling
allure-testopsMCP (already connected) — the richest source. Validated calls:list_launches(projectId: 1, search: "<run_id or name fragment>", sort: ["createdDate,DESC"])orsearch_launches(rql: …)— find the launch.list_test_results(launchId)— per-testname,fullName(spec path + line, e.g.datasets/dataset-crud-smoke.spec.ts:8:7),status, a TestOps-computedflakyflag,muted/known,tags,jobRun.url(the GitHub Actions run), and the resultid. Usesearchto filter to the failing test.get_test_result_history(id)— the pass/fail timeline for that test across recent launches. This is the flake signal.
gh—gh run view <run-id>to find the failed job;gh run download <run-id> -n test-results-v2 -D <dir>for the trace artifact. A launch'sjobRun.urlgives you the run id.npx playwright show-trace <trace.zip>(fromtests_end_to_end/e2e/) — open the trace to see the exact step that failed, the DOM snapshot, and console/network at that moment.git— diff the suspected change against the failing test's code path.
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 · 99 lines · 122 tokens per session scan A d5d0eb84d1c4
debugging-e2e-tests is a skill published in the GitHub repository comet-ml/opik (22,998 stars, last pushed today), licensed Apache-2.0. It adds 122 tokens to every session and 1,860 once invoked, about $0.0005 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
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
code-review
Reviews code for bugs, security issues, and best practices.
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.
agent-debug-fixer
A Chinese-language debugging and repair workflow for software problems. It investigates errors, failed tests, broken pages, or behavior that does not match expectations, then makes a minimal fix.
sentry-app-setup
Create and configure a Sentry internal integration so the assistant can manage issues, alerts, and releases under its own identity.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.