webapp-testing

webapp-testing is a skill for Claude Code from flonat/flonat-research. It costs 48 tokens per session (1,181 once invoked), scanned A, original, MIT.

A testing workflow for a running local web application using Playwright, a tool that controls a browser from code. It can manage local servers and check user flows and what the browser displays.

In plain words
What is it for?
Use it to test login, forms, navigation, and other end-to-end user journeys in a local web app.
Why use it?
It replaces fragile manual checks with repeatable browser tests and custom assertions. It is aimed at full application behaviour rather than a single ad hoc browser action.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: $skill-name invocation.

Good fit Use it to test login, forms, navigation, and other end-to-end user journeys in a local web app.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/flonat/flonat-research/webapp-testing
Install

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.

Any agent
npx skills add flonat/flonat-research --skill webapp-testing
Clone the repo
git clone --depth 1 https://github.com/flonat/flonat-research

Made for: Claude Code.

Wrote 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.

agentmods badge for webapp-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/flonat/flonat-research/webapp-testing/github.svg)](https://agentmods.dev/skills/flonat/flonat-research/webapp-testing)
Your own site
<a href="https://agentmods.dev/skills/flonat/flonat-research/webapp-testing"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/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.

agentmods 80×15 button for webapp-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/flonat/flonat-research/webapp-testing"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/webapp-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,181 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.01181
Opus 5.5 $0.00019 $0.00472
Sonnet 5.5 $0.00010 $0.00236
Haiku 4.5 $0.00005 $0.00118

Measured 25d ago against content hash d3366b309744, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 25d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (examples/console_logging.py, examples/element_discovery.py, examples/static_html_automation.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/webapp-testing/SKILL.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 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.

Use this skill when the task needs local server lifecycle management, custom Python assertions, or a repeatable test script. For ad-hoc browser navigation and interaction that does not need custom Python, use $playwright-cli.

Helper Scripts Available:

  • scripts/with_server.py - Manages server lifecycle (supports multiple servers)

Always run helper scripts with --help first to see usage. DO NOT read the source until you try running the helper and find that a customized solution is absolutely necessary. These scripts can be very large and thus pollute your context window. They exist to be called directly as black-box scripts rather than ingested into your context window.

Dependency Preflight

Before writing a native Playwright script, verify the selected project environment:

uv run python -c "from importlib.metadata import version; print(version('playwright'))"

If the import fails:

  1. For a one-off page inspection without custom assertions, use the declared $playwright-cli fallback.

  2. For repeatable assertions or managed server testing, ask before installing dependencies. After approval, install into the project's development environment rather than adding a browser runtime to production dependencies:

    uv pip install --python <project>/.venv/bin/python playwright
    uv run python -m playwright install chromium
    
  3. Re-run the import preflight, then continue with native Python Playwright.

If the project already declares a Playwright dev extra, prefer syncing that extra over an ad-hoc environment install. Never use bare pip or a machine-global Python environment.

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 → Run: uv run python scripts/with_server.py --help
        │        Then use the helper + write simplified 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

Read the full file on GitHub · 130 lines

Files

What ships with it

5 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.

Changes

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.

  1. 25d ago First seen · 130 lines · 48 tokens per session scan A d3366b309744

Subscribe to this mod's changes

webapp-testing is a skill published in the GitHub repository flonat/flonat-research (146 stars, last pushed 19d ago), licensed MIT. It adds 48 tokens to every session and 1,181 once invoked, about $0.0002 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-23.

Related

Other skills, from other repositories

browser-qa-delivery

Validate a Design Studio HTML artifact in the sandbox browser, fix rendering and runtime defects, then deliver exactly the tested file.

juspay/xyne-spaces · 30 tokens

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.

travisjneuman/.claude · 76 tokens

playwright-pro

Production-grade Playwright testing skill for E2E suites, flaky test diagnosis, browser automation, migration from Cypress/Selenium, CI integration, visual checks, and regression validation.

seaworld008/Commonly-used-high-value-skills · 39 tokens

cypress-ops

Cypress end-to-end and component testing operations - selector/retry-ability strategy, cy.intercept network stubbing, cy.session auth, component vs e2e, flake diagnosis, CI, Test Replay. Use for: cypress, e2e test, component test, cy.get, cy.intercept, cy.session, data-cy, data-test, retry-ability, flake, flaky test…

0xDarkMatter/claude-mods · 104 tokens

playwright-ops

Playwright end-to-end testing operations - selectors, fixtures, network mocking, auth, parallelism, CI, visual regression, flake hunting. Use for: playwright, e2e test, end-to-end testing, browser test, getByRole, page object, storageState, trace viewer, flaky test, test sharding, visual regression, toHaveScreenshot…

0xDarkMatter/claude-mods · 85 tokens

webapp-testing

To test local web applications, write native Python Playwright scripts.

LiHongwei-cn/lihongwei-cn · 17 tokens