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/r5rana/agentware/ui-verificationnpx skills add r5rana/agentware --skill ui-verificationgit clone --depth 1 https://github.com/r5rana/agentwareWrote 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/r5rana/agentware/ui-verification)<a href="https://agentmods.dev/skills/r5rana/agentware/ui-verification"><img src="https://agentmods.dev/badge/skills/r5rana/agentware/ui-verification.svg" alt="Measured on agentmods" 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.00000 | $0.02078 |
| Opus 5 | $0.00000 | $0.01039 |
| Sonnet 5 | $0.00000 | $0.00416 |
| Haiku 4.5 | $0.00000 | $0.00208 |
Grade A, and why
ui-verification 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 6d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Verification Skill — Playwright
When to invoke: when a task changes UI behavior, page rendering, or web-API interactions. ALWAYS ask the user first; never run E2E checks unprompted.
Why this skill exists
Marking a UI task "complete" because the build and unit tests pass is risky — units don't catch routing bugs, hydration issues, race conditions on real network calls, broken visual states, or wrong API payloads. A real browser hitting the real running app is the only honest "complete" for a UI task. This skill is gated on user consent at every checkpoint.
Prerequisites
- The target web app has Playwright installed and a
playwright.config.*. If onboarding's Step 6 ran, it is set up; otherwise run the "Manual setup" at the end of this file. - The configuration entry recording the web-app path and runner command lives at
<KDIR>/configurations/playwright.md(whereKDIR=$(scripts/agentware config --knowledge-dir-only)). Read it before running any spec — paths differ per user. - The web app is runnable locally. Prefer letting
playwright.config.*manage the dev server via itswebServerblock.
When to ask the user
Before marking a UI-affecting task complete in the worklog, ALWAYS ask:
"This task touches the UI. Want me to run a Playwright check before marking it complete? (y/n; default: n)"
- If no: mark complete, but note in the worklog that the E2E check was deferred. Do not silently skip.
- If yes: ask which depth to run.
Depth modes
| Mode | What it does | Default when |
|---|---|---|
| shallow | Render + visible-element assertions | Pure visual / styling change |
| with-api | Shallow + intercept the relevant API request, assert payload + status | Any change touching a fetch / form submit / mutation |
| deep | With-API + multi-step user flow + state mutations | Complex flows, sequential-interaction bug fixes |
If unsure, default to with-api when the change involves a network call, else shallow.
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.
- 6d ago First seen · 221 lines · 0 tokens per session scan A 1a6ce388b3f6
ui-verification is a skill published in the GitHub repository r5rana/agentware (24 stars, last pushed 19d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,078 tokens. 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
browse
Fast headless browser for QA testing and site dogfooding. (gstack).
playwright-dev
Explains how to develop Playwright - add APIs, MCP tools, CLI commands, and vendor dependencies.
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
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.
playwright-cli
官方Microsoft Playwright CLI网页自动化工具，支持所有主流浏览器的无头/有头自动化操作，包括页面导航、元素交互、截图、录制、测试等功能。当用户提到网页自动化、浏览器操作、爬虫、截图、录制用户操作、E2E测试时触发。.
playwright-screen-recording
Record browser test videos with Playwright for PR review and bug fix verification.