webapp-testing

webapp-testing is a skill for Claude Code, Codex from LuizEduPP/Rememb. It costs 31 tokens per session (556 once invoked), scanned A, original, MIT.

A Playwright-based toolkit for testing web applications. Playwright is a browser-automation tool that can inspect pages, click controls, capture screenshots, and read browser output.

In plain words
What is it for?
Checking frontend behavior, debugging user-interface problems, capturing screenshots, inspecting the page structure, and viewing browser logs.
Why use it?
It helps verify what a web app actually renders and how it behaves, including pages whose content appears only after JavaScript runs.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Checking frontend behavior, debugging user-interface problems, capturing screenshots, inspecting the page structure, and viewing browser logs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/luizedupp/rememb/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 LuizEduPP/Rememb --skill webapp-testing
Clone the repo
git clone --depth 1 https://github.com/LuizEduPP/Rememb

Made for: Claude Code, Codex.

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/luizedupp/rememb/webapp-testing/github.svg)](https://agentmods.dev/skills/luizedupp/rememb/webapp-testing)
Your own site
<a href="https://agentmods.dev/skills/luizedupp/rememb/webapp-testing"><img src="https://agentmods.dev/badge/skills/luizedupp/rememb/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/luizedupp/rememb/webapp-testing"><img src="https://agentmods.dev/badge/skills/luizedupp/rememb/webapp-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 556 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.00031 $0.00556
Opus 5.5 $0.00012 $0.00222
Sonnet 5.5 $0.00006 $0.00111
Haiku 4.5 $0.00003 $0.00056

Measured 1mo ago against content hash 7faef3a65a21, 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 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.

src/rememb_skills/webapp-testing/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Web Application Testing

Test web applications using Python Playwright scripts.

Decision Tree

User task → Is it static HTML?
    ├─ Yes → Read HTML file directly for selectors
    │         └─ Write Playwright script
    │
    └─ No (dynamic webapp) → Is server already running?
        ├─ No → Start server first, then test
        │
        └─ 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

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
    
    # Reconnaissance
    page.screenshot(path='/tmp/inspect.png', full_page=True)
    
    # Actions
    page.click('button#submit')
    
    browser.close()

Reconnaissance Pattern

  1. Inspect DOM:

    page.screenshot(path='/tmp/inspect.png', full_page=True)
    content = page.content()
    page.locator('button').all()
    
  2. Identify selectors from results

  3. Execute actions with discovered selectors

Common Pitfall

❌ Inspect DOM before waiting for networkidle ✅ Always page.wait_for_load_state('networkidle') first

Best Practices

  • Use sync_playwright() for synchronous scripts
  • Always close browser when done
  • Use descriptive selectors: text=, role=, CSS, IDs
  • Add waits: wait_for_selector(), wait_for_timeout()
  • Launch chromium in headless=True mode

Overview

Use this skill for the capability described in this document.

When to Use

Use this skill when the request matches the capability, constraints, and activation cues described below.

Core Workflow

Follow the primary workflow, commands, and decision points documented in the sections below.

Read the full file on GitHub · 92 lines

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. 1mo ago First seen · 92 lines · 31 tokens per session scan A 7faef3a65a21

Subscribe to this mod's changes

webapp-testing is a skill published in the GitHub repository LuizEduPP/Rememb (5 stars, last pushed 12d ago), licensed MIT. It adds 31 tokens to every session and 556 once invoked, about $0.0001 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.

Related

Other skills, from other repositories