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 alebgl77/claude-inc --skill webapp-testinggit clone --depth 1 https://github.com/alebgl77/claude-incWrote 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/alebgl77/claude-inc/webapp-testing)<a href="https://agentmods.dev/skills/alebgl77/claude-inc/webapp-testing"><img src="https://agentmods.dev/badge/skills/alebgl77/claude-inc/webapp-testing.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 3 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium MCP Rug Pull · line 23 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 27 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 48 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00103 | $0.00898 |
| Opus 5 | $0.00051 | $0.00449 |
| Sonnet 5 | $0.00021 | $0.00180 |
| Haiku 4.5 | $0.00010 | $0.00090 |
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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: Browser-tests a local webapp end to end — starts the app, installs Playwright if missing, writes a spec for the critical path plus edge cases, runs headless, captures screenshots, console and network logs on How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webapp Testing — QA Engineer
"Browser-test your app"
If a human can click it, it can break. Prove the critical path in a real browser before anything ships.
When to use
- "Test my app" / "check the site before I deploy" — the pre-ship confidence run
- "Does signup still work?" after touching auth, forms, or routing
- "This page is blank" / "the button does nothing" — reproduce with evidence, not vibes
- Regression pass after a dependency bump, refactor, or CSS overhaul
- The project has zero e2e coverage and needs a first spec to seed CI
Workflow
- Start the app in the background (
npm run dev,uvicorn app:app,rails s, ...) and poll until it answers —curl -sf http://localhost:<port>in a retry loop. Never test a dead server. - Ensure Playwright:
npx playwright --version; if missing,npm i -D @playwright/test && npx playwright install chromium. - Map the critical path from the app's purpose: load → key action (signup, add-to-cart, submit) → expected end state.
- Add 2–3 edge cases: invalid input, empty state, refresh mid-flow, double-submit.
- Write
tests/e2e.spec.tsasserting on visible text and roles (getByRole,getByText) — never brittle CSS selector chains. - Run headless:
npx playwright test --reporter=line. - On any failure capture the trio — screenshot, console errors, failed network requests — into
test-results/and reference each by path. - Report the pass/fail table (format below) with exact repro steps per failure.
- No browser possible (install blocked, sandboxed env)? Degrade gracefully: build a curl smoke suite — status code per route, key strings in bodies, form POST round-trips — and label the report
mode: curl-fallback.
Output format
## QA report — <app> @ http://localhost:<port> (mode: playwright-chromium | curl-fallback)
| # | Scenario | Result | Evidence |
|---|----------|--------|----------|
| 1 | Signup happy path | PASS | — |
| 2 | Invalid email rejected | FAIL | test-results/02-invalid-email.png |
Failures:
2. Invalid email rejected
Repro: goto /signup → fill email "nope" → click Submit
Expected: inline validation error
Actual: HTTP 500; console TypeError at validate.js:14; POST /api/signup → 500
Re-run: npx playwright test --reporter=line
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 · 72 lines · 103 tokens per session scan A 3a1150866b34
webapp-testing is a skill published in the GitHub repository alebgl77/claude-inc (14 stars, last pushed 5d ago), licensed MIT. It adds 103 tokens to every session and 898 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
verify
How to run and drive this app to verify UI/server changes at runtime.
dogfood
Exploratory QA of web apps: find bugs, evidence, reports.
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.
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
agent-browser
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.