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 KhaledSaeed18/dotclaude --skill webapp-testinggit clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/webapp-testing)<a href="https://agentmods.dev/skills/khaledsaeed18/dotclaude/webapp-testing"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/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/khaledsaeed18/dotclaude/webapp-testing"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/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.00068 | $0.01400 |
| Opus 5.5 | $0.00027 | $0.00560 |
| Sonnet 5.5 | $0.00014 | $0.00280 |
| Haiku 4.5 | $0.00007 | $0.00140 |
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 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.
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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test the application in a real browser rather than claiming it works from a code read alone. A passing type-check or unit test does not mean the page renders, the form submits, or the network request succeeds. Run the app, drive it with Playwright, and report what actually happened.
Step 1: Check for Playwright and a running app
# Check if Playwright is installed
npx playwright --version 2>/dev/null || echo "not installed"
# Check if there is an existing Playwright config
ls playwright.config.ts playwright.config.js 2>/dev/null
If Playwright is not installed, install it:
npm install --save-dev @playwright/test
npx playwright install chromium
Check whether the dev server is already running. If not, start it before writing tests. Use the project's start script - check package.json for the correct command (npm run dev, npm start, etc.). The server must be running for Playwright to connect.
Step 2: Identify what to verify
Before writing any test, state the scenario in plain terms:
- What page or URL does the scenario start from?
- What actions does the user take? (navigate, click, type, submit, wait)
- What is the expected outcome? (page title changes, element appears, URL changes, form resets, API call completes)
- Are there any states to verify along the way? (loading indicator, validation message, success confirmation)
If the user has not specified a scenario, default to: navigate to the app's root, confirm it loads without console errors, and take a screenshot.
Step 3: Write the Playwright script
Write a focused script that tests the specified scenario. Keep each script to one scenario.
import { chromium } from "@playwright/test";
const browser = await chromium.launch({ headless: true });
const context = await browser.newContext({
viewport: { width: 1280, height: 720 },
});
const page = await context.newPage();
// Collect console errors throughout the session
const consoleErrors: string[] = [];
page.on("console", (msg) => {
if (msg.type() === "error") consoleErrors.push(msg.text());
});
// Collect failed network requests
const networkErrors: string[] = [];
page.on("requestfailed", (request) => {
networkErrors.push(`${request.method()} ${request.url()} - ${request.failure()?.errorText}`);
});
try {
// Navigate and wait for the page to be ready
await page.goto("http://localhost:3000", { waitUntil: "networkidle" });
// Take a screenshot of the initial state
await page.screenshot({ path: "screenshot-initial.png", fullPage: true });
// Example: verify a heading is present
const heading = await page.locator("h1").first().textContent();
console.log(`Page heading: ${heading}`);
// Example: fill and submit a form
// await page.fill('[name="email"]', '[email protected]');
// await page.fill('[name="password"]', 'test-password');
// await page.click('[type="submit"]');
// await page.waitForURL('**/dashboard');
// Take a final screenshot
await page.screenshot({ path: "screenshot-final.png", fullPage: true });
console.log("Console errors:", consoleErrors.length === 0 ? "none" : consoleErrors);
console.log("Network errors:", networkErrors.length === 0 ? "none" : networkErrors);
} finally {
await browser.close();
}
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 Changed · -23 tokens per session 10e74d8fdbab
- 1mo ago First seen · 157 lines · 91 tokens per session scan A f3daf9fa2d84
webapp-testing is a skill published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 3d ago), licensed MIT. It adds 68 tokens to every session and 1,400 once invoked, about $0.0003 per session on Opus 5.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
browser-test-loop
Use to actually verify a web change in a real browser instead of assuming it works — click through a flow, catch console errors, check a form submits, confirm a fix on the page. Trigger when a UI change needs proof, a bug only reproduces in the browser, or the user asks to test, check, or screenshot the running app.
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.
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.
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.
shipkit-qa-visual
Visual QA using Playwright as a browser automation library. --setup installs Playwright and creates ui-goals.json; default mode writes inline scripts to navigate, screenshot, and report against goals.