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 agentmods add skills/comet-ml/opik/debugging-e2e-testsnpx skills add comet-ml/opik --skill debugging-e2e-testsgit clone --depth 1 https://github.com/comet-ml/opikWhat 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 | $0.00122 | $0.01860 |
| Opus 5 | $0.00061 | $0.00930 |
| Sonnet 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 yesterday.
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.
- yesterday 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 (21,685 stars, last pushed yesterday), licensed Apache-2.0. It adds 122 tokens to every session and 1,860 once invoked, about $0.0006 per session on Opus 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
swarms
Build agents and multi-agent systems with the Swarms framework — the Agent class, tools, autonomous loops, memory, and the 15+ multi-agent architectures (SequentialWorkflow, ConcurrentWorkflow, GraphWorkflow, HierarchicalSwarm, SwarmRouter, and more). Use whenever writing, reviewing, or debugging code that imports…
greeting-user
Explains how to properly greet the user.
code-review
Perform comprehensive code reviews focusing on best practices, security vulnerabilities, performance optimization, and maintainability.
using-process-tool
Describes how to correctly use 'process' tool.
data-visualization
Create effective data visualizations using best practices for clarity, accuracy, and visual communication of insights.
financial-analysis
Perform comprehensive financial analysis including DCF modeling, ratio analysis, and financial statement evaluation for companies and investment opportunities.