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 squadcodercom/squadcoder --skill webapp-testinggit clone --depth 1 https://github.com/squadcodercom/squadcoderWrote 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/squadcodercom/squadcoder/webapp-testing)<a href="https://agentmods.dev/skills/squadcodercom/squadcoder/webapp-testing"><img src="https://agentmods.dev/badge/skills/squadcodercom/squadcoder/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/squadcodercom/squadcoder/webapp-testing"><img src="https://agentmods.dev/badge/skills/squadcodercom/squadcoder/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.00115 | $0.00785 |
| Opus 5.5 | $0.00046 | $0.00314 |
| Sonnet 5.5 | $0.00023 | $0.00157 |
| Haiku 4.5 | $0.00012 | $0.00078 |
Grade A, and why
sc: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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webapp Testing — resilient end-to-end tests with Playwright
Test what the user sees and does, not implementation details. The bundled Playwright MCP/browser is available; use it to drive a real browser and assert on real state.
Step 0 — decide the flow
Name the user journey ("sign up → onboarding → first project"). Test that, not isolated widgets. List the success assertions up front (what must be true at the end).
Step 1 — resilient selectors (in priority order)
- Role + accessible name —
getByRole("button", { name: "Save" }). Survives restyles. - Visible text —
getByText(...). - Label / placeholder — for form fields.
data-testid— only when the above can't disambiguate. Avoid brittle CSS/XPath chains and nth-child positional selectors.
Step 2 — wait on conditions, never sleep
- Use auto-waiting assertions:
await expect(locator).toBeVisible(),toHaveText,toHaveURL. - Never
waitForTimeout(n)to "let it settle" — wait for the actual condition (element, response, URL). - For network:
await page.waitForResponse(/api\/thing/)when an action triggers a fetch.
Step 3 — drive the flow and assert
await page.goto(BASE_URL)
await page.getByRole("button", { name: "Open project" }).click()
await page.getByPlaceholder("Browse folders").fill("~/demo")
await page.keyboard.press("Enter")
await expect(page.getByRole("heading", { name: "demo" })).toBeVisible()
Step 4 — catch errors the user wouldn't report
- Console: fail the test on
console.error/ uncaught exceptions (page.on("console")/"pageerror"). - Network: flag 4xx/5xx on requests the flow depends on.
- A11y: check focus order and that interactive elements have accessible names.
Step 5 — visual + RTL/Hebrew parity
- Screenshot key states; compare to a baseline (
toHaveScreenshot) with a small tolerance. - Always test RTL too: load the app in Hebrew (
dir="rtl"), verify the sidebar/layout mirror and nothing overlaps. RTL bugs hide in physical-CSS leftovers — this catches them. - Test at mobile and desktop widths if the app is responsive.
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 · 61 lines · 115 tokens per session scan A 9c41a9d5f0ff
sc:webapp-testing is a skill published in the GitHub repository squadcodercom/squadcoder (12 stars, last pushed 3mo ago), licensed MIT. It adds 115 tokens to every session and 785 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
hatch3r-browser-verify
Opt-in browser verification skill — spec-run-first Playwright verification (assertions execute in the runner, agent reads only failures), axe-core a11y audits, toHaveScreenshot() regression diffs, E2E test scaffolds, and snapshot-mode exploratory driving. Default ON for UI-affecting agent invocations; disable globally…
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
BrowserBash Browser Automation
BrowserBash is a vendor-independent, natural-language browser automation CLI. Drive a real browser from plain-English objectives or committable Markdown tests, run on local Chrome, CDP/Playwright MCP, Browserbase, LambdaTest, or BrowserStack, and stream NDJSON results with CI exit codes — using free local Ollama…
test-app
Verify a running Mendix app in a browser: mxcli playwright check for a one-call text verdict per page (renders? error banner? console errors? rows?), playwright-cli scripts for interaction, OQL for data. Use when asked to check a page, see whether it renders, verify in the browser, test the app end to end, or confirm…
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…
checking-a-page
Check that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it. Use after creating or editing an HTML page, or the JavaScript or CSS that a page loads.