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 kok-o/contextos-agents --skill webapp-testinggit clone --depth 1 https://github.com/kok-o/contextos-agentsWrote 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/kok-o/contextos-agents/webapp-testing)<a href="https://agentmods.dev/skills/kok-o/contextos-agents/webapp-testing"><img src="https://agentmods.dev/badge/skills/kok-o/contextos-agents/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/kok-o/contextos-agents/webapp-testing"><img src="https://agentmods.dev/badge/skills/kok-o/contextos-agents/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.00027 | $0.00603 |
| Opus 5.5 | $0.00011 | $0.00241 |
| Sonnet 5.5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
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 yesterday.
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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test a local web application
Overview
Turn a user flow or reported UI bug into reproducible browser evidence. This ContextOS adaptation references Anthropic's webapp-testing skill; see source provenance and license.
When to Use
Verify a local site, reproduce a browser-only failure, inspect responsive states, or check a frontend change in Playwright. Use the environment's supported browser tools and the project's test runner; this skill does not override tool-access restrictions or require one programming language.
Rules & Patterns
Inspect existing scripts, Playwright configuration and the target route. Define the expected result and important failure path. Use an already running local server when appropriate; otherwise start the project's documented command and wait for a bounded readiness signal. Track processes started for this task and clean them up without stopping unrelated services.
Inspect rendered elements and use stable role/name/label locators. Rely on Playwright's auto-waiting and web-first assertions for the actual state. Do not use fixed sleeps or networkidle as a universal readiness requirement: polling, analytics or streaming may remain active while the tested UI is ready.
Exercise the real interaction and assert its visible result. Check a relevant error/empty case, keyboard focus, narrow viewport or reduced-motion mode when the change affects it. Collect console/page errors and useful screenshots or traces. A screenshot confirms appearance in that capture, not the success of an unasserted interaction or complete accessibility.
Use deterministic local test data. Keep credentials and private data out of screenshots, traces and logs. Use test accounts for state-changing flows; existing authorization and environment boundaries govern any external side effect.
Code Examples
For a settings form, fill controls by label, submit by role/name and assert both the saved state and the failure message for a controlled rejected save. See references/playwright.md for a minimal test pattern and its prerequisites; no helper script is assumed to exist in this skill.
What ships with it
4 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.
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.
- yesterday First seen · 69 lines · 27 tokens per session scan A 0ca5f7a44b3c
webapp-testing is a skill published in the GitHub repository kok-o/contextos-agents (10 stars, last pushed 2d ago), licensed Apache-2.0. It adds 27 tokens to every session and 603 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-10-29.
Other skills, from other repositories
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
qa/e2e-playwright
A method for writing Playwright end-to-end tests, which automate a browser to verify complete user journeys. It covers setup, reusable page objects, login reuse, API mocking, visual checks, multiple browsers and screen sizes, CI, and debugging.
playwright-visual-testing
Add, repair, or review Playwright visual regression tests for browser-facing .NET apps, including screenshot baselines, Pixelmatch thresholds, deterministic rendering, and GitHub Actions artifacts. USE FOR: toHaveScreenshot, page.screenshot visual checks, Pixelmatch/pngjs comparison scripts, visual baseline updates…
ui-regression
This skill should be used when the user asks to "verify UI changes", "audit UI quality", "test every screen and action", "run regression QA", "check a deployed UI", or "validate an extension release". Test known web and browser-extension workflows on localhost, staging, or production with action coverage, recovery…
run-qa
This skill should be used when user asks to "run QA", "verify real playback", "test provider connections", or "check website, extension or Android flows" with tracked journeys.