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 floomhq/moto --skill webapp-testinggit clone --depth 1 https://github.com/floomhq/motoWrote 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/floomhq/moto/webapp-testing)<a href="https://agentmods.dev/skills/floomhq/moto/webapp-testing"><img src="https://agentmods.dev/badge/skills/floomhq/moto/webapp-testing/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/floomhq/moto/webapp-testing"><img src="https://agentmods.dev/badge/skills/floomhq/moto/webapp-testing.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.00035 | $0.00830 |
| Opus 5.5 | $0.00014 | $0.00332 |
| Sonnet 5.5 | $0.00007 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
webapp-testing scanned grade A with 1 finding 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 1mo 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
server = subprocess.Popen(["npm", "run", "dev"]) How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Application Testing
To test local web applications, write native Python Playwright scripts.
Decision Tree: Choosing Your Approach
User task → Is it static HTML?
├─ Yes → Read HTML file directly to identify selectors
│ ├─ Success → Write Playwright script using selectors
│ └─ Fails/Incomplete → Treat as dynamic (below)
│
└─ No (dynamic webapp) → Is the server already running?
├─ No → Start the server first, then write Playwright script
└─ Yes → Reconnaissance-then-action:
1. Navigate and wait for networkidle
2. Take screenshot or inspect DOM
3. Identify selectors from rendered state
4. Execute actions with discovered selectors
Starting a Server for Testing
# Start server in background, wait for it to be ready, then run automation
npm run dev &
sleep 3
python automation.py
Or manage the server lifecycle in the script itself:
import subprocess
import time
server = subprocess.Popen(["npm", "run", "dev"])
time.sleep(3) # Wait for server to start
try:
# Run automation
pass
finally:
server.terminate()
Basic Playwright Script
from playwright.sync_api import sync_playwright
with sync_playwright() as p:
browser = p.chromium.launch(headless=True)
page = browser.new_page()
page.goto('http://localhost:5173')
page.wait_for_load_state('networkidle') # CRITICAL: Wait for JS to execute
# Take screenshot for inspection
page.screenshot(path='/tmp/inspect.png', full_page=True)
# Inspect DOM
content = page.content()
# Execute actions
page.click('button:has-text("Submit")')
page.fill('input[name="email"]', '[email protected]')
# Assert results
assert page.locator('.success-message').is_visible()
browser.close()
Reconnaissance-Then-Action Pattern
- Inspect rendered DOM:
page.screenshot(path='/tmp/inspect.png', full_page=True) content = page.content() buttons = page.locator('button').all()
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.
- 1mo ago First seen · 132 lines · 35 tokens per session scan A 140d1bbf0780
webapp-testing is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 830 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
playwright
Playwright end-to-end testing best practices for web applications, covering test design, locator strategies, and assertion patterns.
playwright-cursor-rules
Expert guidance for Playwright end-to-end testing with TypeScript and JavaScript best practices.
browser-qa
A live browser quality-checking workflow that replays user journeys with Playwright-compatible scripts, screenshots, and reports. It stores test cases and run evidence under `.agents/qa/`.
agent-e2e-test-specialist
Specialist subagent: Playwright, Cypress, and visual regression testing specialist. Use only when the user explicitly asks for E2E tests, browser test automation, or visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.