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/vibeinging/yiyi/webapp_testingnpx skills add vibeinging/YiYi --skill webapp_testinggit clone --depth 1 https://github.com/vibeinging/YiYiWrote 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/vibeinging/yiyi/webapp_testing)<a href="https://agentmods.dev/skills/vibeinging/yiyi/webapp_testing"><img src="https://agentmods.dev/badge/skills/vibeinging/yiyi/webapp_testing.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 | $0.00035 | $0.00334 |
| Opus 5 | $0.00017 | $0.00167 |
| Sonnet 5 | $0.00007 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
webapp_testing 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 4d 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.
What it actually says
Web Application Testing
To test local web applications, write native Python Playwright scripts.
Helper Scripts
scripts/with_server.py- Manages server lifecycle (supports multiple servers)
Always run scripts with --help first.
Decision Tree
User task → Is it static HTML?
├─ Yes → Read HTML file directly, write Playwright script
└─ No (dynamic webapp) → Is the server already running?
├─ No → Use scripts/with_server.py helper
└─ Yes → Reconnaissance-then-action pattern
Example: Using with_server.py
python scripts/with_server.py --server "npm run dev" --port 5173 -- python your_automation.py
Reconnaissance-Then-Action Pattern
- Navigate and wait for networkidle
- Take screenshot or inspect DOM
- Identify selectors from rendered state
- Execute actions with discovered selectors
Best Practices
- Use
sync_playwright()for synchronous scripts - Always close the browser when done
- Use descriptive selectors:
text=,role=, CSS selectors, or IDs - Always wait for
networkidlebefore inspecting dynamic apps
What ships with it
4 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.
- 4d ago First seen · 52 lines · 35 tokens per session scan A 8a01bd0545bb
webapp_testing is a skill published in the GitHub repository vibeinging/YiYi (51 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 334 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
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
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…
playwright-screen-recording
Record browser test videos with Playwright for PR review and bug fix verification.
web-preview
Flutter Web版をビルド → サーバー起動 → Playwright でアクセス確認 → URLをユーザーに案内する。.
login-flows
Common login automation patterns for web apps using Playwright.