AG-UI is an event-based protocol that lets AI agent backends communicate with user-facing applications. It standardizes agent events and inputs while supporting transports such as server-sent events, WebSockets, and webhooks. The catalogue add-ons help developers build integrations and applications around the protocol.
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/ag-ui-protocol/ag-ui/agui-playwright-validatenpx skills add ag-ui-protocol/ag-ui --skill agui-playwright-validategit clone --depth 1 https://github.com/ag-ui-protocol/ag-uiWrote 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/ag-ui-protocol/ag-ui/agui-playwright-validate)<a href="https://agentmods.dev/skills/ag-ui-protocol/ag-ui/agui-playwright-validate"><img src="https://agentmods.dev/badge/skills/ag-ui-protocol/ag-ui/agui-playwright-validate.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.00199 | $0.01466 |
| Opus 5 | $0.00100 | $0.00733 |
| Sonnet 5 | $0.00040 | $0.00293 |
| Haiku 4.5 | $0.00020 | $0.00147 |
Grade A, and why
agui-playwright-validate 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright MCP Validation
Technique skill for manually validating a live web app or docs site through
the playwright MCP server (configured in this repo's .mcp.json as
@playwright/mcp@latest). The agent calls the browser_* MCP tools directly —
never write or wrap them in scripts. This captures the validated workflow
used to verify the docs sidebar icon and dojo pages, including the gotchas an
agent otherwise rediscovers slowly.
When to reach for this
Use Playwright-MCP validation for what a unit test can't give you:
- Confirming something actually renders (layout, an icon/SVG, a color).
- Verifying interactive states — hover, click, theme toggle, dialogs.
- Catching console errors that only surface in a real browser.
- Producing a screenshot for a human to eyeball a visual change.
If a deterministic assertion in code would suffice, write a test instead.
Prerequisites
- The app/docs site must be running. If you start a dev server, note the port and URL; you own stopping it during cleanup.
- The
playwrightMCP server must be connected (itsbrowser_*tools appear in your tool list). On first use it may install a browser — allow time.
Validation loop
Cheap-to-expensive. Stop as soon as you have a confident answer.
- Navigate —
browser_navigateto the page URL. - Snapshot —
browser_snapshotreturns the accessibility tree (text + roles + refs). This is token-cheap and the primary assertion surface. Confirm the expected heading/text/landmark is present here before screenshotting. - Console —
browser_console_messagesand assert 0 errors (warnings may be acceptable; judge by context). Do this on every page you validate. - Screenshot —
browser_take_screenshotonly when a human needs to see it, or when a visual detail can't be asserted from the tree (color, spacing, image rendering). - Report pass/fail per check with the concrete evidence (the heading text you saw, the console count, the computed color).
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 · 147 lines · 199 tokens per session scan A e50b35984f67
agui-playwright-validate is a skill published in the GitHub repository ag-ui-protocol/ag-ui (15,743 stars, last pushed yesterday), licensed MIT. It adds 199 tokens to every session and 1,466 once invoked, about $0.0010 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
tutti-record-agent-session-replay
From a Tutti checkout, run, audit, freshly replay, publish, or diagnose Session Replay cassettes that are driven by case-repository scenario scripts (CDP), not by interactive UI recording. Use for real-Provider capture while a scenario.mjs executes, cassette transport or semantic-state mismatches, fresh replay…
test-engineer
Automated E2E testing with Playwright including the auto-fix loop — generate test cases from the UI, run them, fix failures and re-run until passing, then produce a human-readable report. Test until it passes, not just test and report. Drives /toh-test; use whenever tests must be written, run, or made green.
browser-automation
Local Python-based browser automation toolkit using Playwright. Provides command-line tools for navigating, interacting with, and testing web applications without using MCP protocols. Supports clicking, typing, hovering, screenshots, content extraction, and JavaScript execution.
browser-automation
Browser automation powers web testing, scraping, and AI agent.
deckforge-visual-evidence
Start a DeckForge application in an isolated browser session, exercise editor/presenter/viewer/export capabilities, capture screenshots, console errors, failed requests, accessibility results, and traces, generate machine-readable evidence, and stop every process the run created. Use for visual QA of generated…
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.