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 skills add atournayre/claude-marketplace --skill ui-testgit clone --depth 1 https://github.com/atournayre/claude-marketplaceWrote 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/atournayre/claude-marketplace/ui-test)<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/ui-test"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/ui-test/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/atournayre/claude-marketplace/ui-test"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/ui-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00047 | $0.03368 |
| Opus 5 | $0.00023 | $0.01684 |
| Sonnet 5 | $0.00009 | $0.00674 |
| Haiku 4.5 | $0.00005 | $0.00337 |
Grade A, and why
ui-test 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 12d 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 — 398 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chrome UI Test Skill
Instructions à Exécuter
IMPORTANT : Exécute ce workflow étape par étape de manière proactive.
Usage
/chrome-ui-test:ui-test <URL> [options]
Arguments :
<URL>: URL de la page à tester (obligatoire)
Options :
--scenario="description": Scénario de test à exécuter (ex: "login avec email/password")--responsive: Tester sur 3 tailles d'écran (mobile 375x667 + tablette 768x1024 + desktop 1920x1080)--mobile: Tester uniquement sur mobile (375x667)--tablet: Tester uniquement sur tablette (768x1024)--desktop: Tester uniquement sur desktop (1920x1080)--visual: Capturer des screenshots pour validation visuelle--debug: Activer le mode debug (console logs, network requests)--gif: Enregistrer un GIF du parcours utilisateur--viewport=WIDTHxHEIGHT: Taille de fenêtre custom (ex: 1366x768)--help: Afficher un résumé des actions qui seront effectuées (avec les options actives) et demander confirmation
Exemples :
# Test simple de navigation
/chrome-ui-test:ui-test https://example.com
# Test d'un scénario de login avec GIF
/chrome-ui-test:ui-test https://app.example.com/login --scenario="login avec credentials valides" --gif
# Test responsive (3 tailles : mobile + tablette + desktop)
/chrome-ui-test:ui-test https://example.com --responsive --visual
# Test mobile uniquement
/chrome-ui-test:ui-test https://m.example.com --mobile --visual
# Test desktop uniquement
/chrome-ui-test:ui-test https://example.com --desktop
# Debug d'une page avec erreurs
/chrome-ui-test:ui-test https://example.com/broken-page --debug
# Voir ce qui sera fait avant de lancer
/chrome-ui-test:ui-test https://example.com --mobile --visual --help
Workflow
Phase -1 : Mode Aide (si --help)
IMPORTANT : Cette phase s'exécute UNIQUEMENT si l'option --help est présente.
- Analyser l'URL et les options
- URL cible : afficher l'URL qui sera testée
- Options actives : lister toutes les options détectées
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 398 lines · 47 tokens per session scan A 9cf0ab2637c3
ui-test is a skill published in the GitHub repository atournayre/claude-marketplace (9 stars, last pushed 6mo ago), licensed MIT. It adds 47 tokens to every session and 3,368 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-31.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
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.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…