writing-visual-tests

writing-visual-tests is a skill for Claude Code, Codex from comet-ml/opik. It costs 108 tokens per session (7,979 once invoked), scanned C, original, Apache-2.0.

A guide for adding screenshot-based checks to Opik, a software tool for monitoring and evaluating AI applications. It covers tests that compare a page or panel’s saved image with a reference image.

In plain words
What is it for?
Adding visual regression tests for Opik pages and panels, including different tabs, trace sidebars, and empty states. It helps organize page objects, test data, screenshot files, and test projects.
Why use it?
It helps catch visual changes that ordinary tests may miss, such as altered layouts, missing elements, or incorrect empty states. It also explains how to create repeatable test data so screenshots can be compared reliably.

Skill for Claude CodeCodex

About the project

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.

comet-ml/opik · 21,768 stars · on GitHub

Install

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.

agentmods
npx agentmods add skills/comet-ml/opik/writing-visual-tests
Any agent
npx skills add comet-ml/opik --skill writing-visual-tests
Clone the repo
git clone --depth 1 https://github.com/comet-ml/opik

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for writing-visual-tests

README.md
[![agentmods](https://agentmods.dev/badge/skills/comet-ml/opik/writing-visual-tests.svg)](https://agentmods.dev/skills/comet-ml/opik/writing-visual-tests)
Your own site
<a href="https://agentmods.dev/skills/comet-ml/opik/writing-visual-tests"><img src="https://agentmods.dev/badge/skills/comet-ml/opik/writing-visual-tests.svg" alt="Measured on agentmods" height="20"></a>
Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,979 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00108 $0.07979
Opus 5 $0.00054 $0.03989
Sonnet 5 $0.00022 $0.01596
Haiku 4.5 $0.00011 $0.00798

Measured 5d ago against content hash ac63c2458fdb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

writing-visual-tests scanned grade C with 2 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 5d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

| `test-results/` | Playwright's per-test output (failure screenshots, videos, traces) | Regenerated every run — safe to delete: `rm -rf test-results`. |

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s http://localhost:5555/health
.agents/skills/writing-visual-tests/SKILL.md · 350 lines

How it starts

The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Writing Visual Tests

This skill adds a screenshot-comparison test to Opik's visual regression suite. Unlike the functional E2E suite (tests_end_to_end/e2e/, see writing-e2e-tests), this suite's assertion is the screenshot — so seeding must produce deterministic pixels, not just correct data.

Announce at start: "I'm using the writing-visual-tests skill to add a visual test for X."

Plan before implementing. Before writing or editing any file, work through step 1 ("Scope") of "The loop" below and present the user a short plan: which page/panel and states you'll cover, what new seed route/client method (if any) you'll add, which spec file and project the new test(s) will live in (and why, per "One project per screenshot group"), and the resulting screenshot name(s). Wait for the user's explicit approval before starting step 2 (seeding) or any other implementation work. Only skip this pause if the user's request already specifies all of these choices unambiguously.

Where tests live

The suite is at tests_end_to_end/visual-tests/:

  • Specs: tests/<area>.spec.ts — e.g. visual-comparison.spec.ts (happy-path pages), empty-states.spec.ts, trace-sidebar.spec.ts. One test.describe per spec, one test.beforeAll that seeds data and resolves the project ID.
  • Page objects: page-objects/<page>.page.ts — see "Page object pattern" below; always follow it, don't freehand a different shape.
  • Seeding: helpers/test-helper-client.ts — a typed HTTP client over the Flask test-helper-service (../test-helper-service/routes/*.py), which wraps the real Python SDK. Add a new route + a new client method together; never seed by clicking through the UI.
  • Screenshot util: tests/utils/screenshot.tsscreenshot(page, name, extraMasks?). Read this whole file before writing a new spec.
  • Global setup/teardown: global-setup.ts / global-teardown.ts — create/delete the fixed-name projects (visual-project, visual-empty-project, visual-sidebar-project, …) used across specs. Fixed names, no timestamp suffix, so screenshots are identical across runs. Give each new portion of screenshots its own project — see "One project per screenshot group" below.
  • Baselines: screenshots/baseline/*.png — see "Baselines are local and gitignored" below before you assume one exists.

Read the full file on GitHub · 350 lines

Changes

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.

  1. 5d ago First seen · 350 lines · 108 tokens per session scan C ac63c2458fdb

Subscribe to this mod's changes

writing-visual-tests is a skill published in the GitHub repository comet-ml/opik (21,768 stars, last pushed yesterday), licensed Apache-2.0. It adds 108 tokens to every session and 7,979 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.