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/microsoft/playwright/playwright-test-resultsnpx skills add microsoft/playwright --skill playwright-test-resultsgit clone --depth 1 https://github.com/microsoft/playwrightWhat 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.00045 | $0.02247 |
| Opus 5 | $0.00023 | $0.01123 |
| Sonnet 5 | $0.00009 | $0.00449 |
| Haiku 4.5 | $0.00005 | $0.00225 |
Grade A, and why
playwright-test-results 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 3d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Test Results (DuckDB)
A single DuckDB file holds recent Playwright CI test results, so you can answer questions about failures, flakiness, and slow tests with plain SQL. It is refreshed every few hours.
Get the database
Download the latest snapshot:
npm ci # first time only, from the repo root
GITHUB_TOKEN=$(gh auth token) node utils/test-results-db/cli.ts download
The snapshot may be missing the newest runs. To top it up locally, run update:
GITHUB_TOKEN=$(gh auth token) node utils/test-results-db/cli.ts update --lookback-days 3
Query it through the bundled @duckdb/node-api binding — no separate DuckDB
install needed, it ships in node_modules after npm ci:
node --input-type=module -e '
import { DuckDBInstance } from "@duckdb/node-api";
const conn = await (await DuckDBInstance.create("utils/test-results-db/test-results.duckdb")).connect();
console.table((await conn.runAndReadAll(process.argv[1])).getRowObjectsJson());
' "SELECT count(*) FROM test_results"
Integer columns come back as strings (JSON-safe), so do ranking and filtering in SQL, not in JS.
Schema
Single table test_results, one row per test result (one row per retry).
The columns are inferred from the parquet the reporter emits
(tests/config/parquetReporter.ts), plus two trailing columns this CLI adds:
| Column | Meaning |
|---|---|
run_id, run_attempt |
GitHub Actions run identity |
run_started_at |
when the run started |
workflow_name |
e.g. tests 1 / tests 2 / tests others / MCP |
event |
push / pull_request |
head_sha, head_branch, pr_number |
what was tested |
bot_name |
e.g. chromium-ubuntu-22.04-node20, webkit-macos-15-large — the CI bot. OS and arch are encoded here; there is no separate os column. |
project_name |
CI project = browser + suite, e.g. chromium-page, webkit-library, playwright-test |
test_title |
title path within the file, joined by › (describe › test) |
file, line, column_number |
source location (file is relative to repo root) |
expected_status |
passed / skipped / ... |
status |
actual result: passed / failed / timedOut / skipped / interrupted |
retry |
0 = first attempt |
result_started_at |
when this attempt started |
duration_ms |
result duration |
error_message |
all errors joined, ANSI-stripped (NULL when none) |
tags |
list of strings, e.g. ['@slow', '@flaky'] (use list functions / list_contains) |
annotations |
list of {type, description} structs, e.g. [{'type': 'skip', 'description': 'flaky on CI'}] (empty list when none) |
artifact_id |
the GitHub artifact this row came from (dedupe key) |
ingested_at |
debug only — when this row was imported |
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.
- 3d ago First seen · 211 lines · 45 tokens per session scan A 3fd24911309f
playwright-test-results is a skill published in the GitHub repository microsoft/playwright (95,493 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 2,247 once invoked, about $0.0002 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
ffmpeg
Video and audio processing with FFmpeg. Use for format conversion, resizing, compression, audio extraction, and preparing assets for Remotion. Triggers include converting GIF to MP4, resizing video, extracting audio, compressing files, or any media transformation task.
playwright-recording
Record browser interactions as video using Playwright. Use for capturing demo videos, app walkthroughs, and UI flows for Remotion videos. Triggers include recording a demo, capturing browser video, screen recording a website, or creating walkthrough footage.
elevenlabs
Generate AI voiceovers, sound effects, and music using ElevenLabs APIs. Use when creating audio content for videos, podcasts, or games. Triggers include generating voiceovers, narration, dialogue, sound effects from descriptions, background music, soundtrack generation, voice cloning, or any audio synthesis task.
ideogram4
Prompting patterns for Ideogram 4 text-to-image — best-in-class in-image text rendering and exact color/layout control via structured JSON captions. Use when generating images that need legible on-image text (title cards, thumbnails, logos, signage, CTAs), precise brand colors, or controlled spatial layout. Triggers…
moli-webfetch
Fetch, inspect, crawl, and capture live, JavaScript-rendered websites with Moli. Use when Codex needs current web content, web research, fact lookup, link following, a bounded crawl, client-rendered or response-gated content, network diagnostics, or a standalone HTML, Markdown, JSON, semantic-tree, viewport or…
browser-automation
Playwright-based browser automation patterns for autonomous web interaction.