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 phuonghx/aim-cli --skill webapp-testinggit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/webapp-testing)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/webapp-testing"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/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/phuonghx/aim-cli/webapp-testing"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/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.00074 | $0.00947 |
| Opus 5.5 | $0.00030 | $0.00379 |
| Sonnet 5.5 | $0.00015 | $0.00189 |
| Haiku 4.5 | $0.00007 | $0.00095 |
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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web App Testing
Find every route before you test any of them. Untested surface is where regressions hide.
Automation
| Script | What it does | How to run |
|---|---|---|
scripts/playwright_runner.py |
Loads a page and reports basic health | python scripts/playwright_runner.py https://example.com |
| ...with a full-page screenshot | python scripts/playwright_runner.py <url> --screenshot |
|
| ...with a quick accessibility pass | python scripts/playwright_runner.py <url> --a11y |
Setup: pip install playwright && playwright install chromium
Audit before you test
Discover the surface first
- Routes -- read
app/,pages/, and router definitions. - API endpoints -- grep for HTTP verbs and route registrations.
- Components -- locate the component directories.
- Features -- skim the docs for what's supposed to exist.
Then work through it
- Map every route and endpoint.
- Probe each one to confirm it responds.
- Cover the critical paths with real tests.
The web testing pyramid
/\ End-to-end (a few)
/ \ critical user journeys
/----\
/ \ Integration (some)
/--------\ API and data flow
/ \
/------------\ Component (many)
individual UI pieces
End-to-end tests
Prioritize
- Happy-path user journeys.
- Sign-in and auth flows.
- The business-critical actions.
- Error and failure handling.
Keep them solid
- Select via
data-testidrather than brittle CSS or text. - Wait on elements/conditions instead of fixed sleeps.
- Start each test from clean state so order never matters.
- Assert on what the user sees, not internal wiring.
Working with Playwright
Building blocks
- Page Object Model -- keep page interactions in one place.
- Fixtures -- share setup across tests.
- Web-first assertions -- they auto-wait, cutting flakiness.
- Trace Viewer -- replay a failed run to see what happened.
What ships with it
1 file 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.
- 1mo ago First seen · 143 lines · 74 tokens per session scan A cfe3099e0eae
webapp-testing is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 3mo ago), licensed MIT. It adds 74 tokens to every session and 947 once invoked, about $0.0003 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
webapp-testing
To test local web applications, write native Python Playwright scripts.
browser
Use when automating browser interactions, web scraping, or E2E UI testing using AI-optimized abbreviated selectors and isolated multi-session contexts.
browser-automation
Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
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.
test-production
Runs bin/test-production.ps1 to acceptance-test a production (or prerelease) release of browser4-cli. Use when asked to run production tests, acceptance-test a release, or verify the published CLI.