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 bugrabilge/bilge-development-kit --skill webapp-testinggit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWrote 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/bugrabilge/bilge-development-kit/webapp-testing)<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/webapp-testing"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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/bugrabilge/bilge-development-kit/webapp-testing"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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.00024 | $0.01935 |
| Opus 5 | $0.00012 | $0.00967 |
| Sonnet 5 | $0.00005 | $0.00387 |
| Haiku 4.5 | $0.00002 | $0.00194 |
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 5d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Application Testing
"Testing leads to failure, and failure leads to understanding." -- Burt Rutan
When to Use
- Setting up end-to-end (E2E) testing for web applications
- Writing or reviewing Playwright or Cypress test suites
- Implementing component testing for React, Vue, or Angular components
- Adding visual regression testing to CI/CD pipelines
- Performing accessibility (a11y) audits and automated checks
- Designing test strategies for web applications
- Debugging flaky or slow tests
Testing Strategy Layers
The Testing Pyramid for Web Apps
- Unit tests (many, fast): Pure logic, utilities, state management, data transforms
- Component tests (moderate): Render components in isolation, test interactions
- Integration tests (moderate): Test connected components, API integration, routing
- E2E tests (few, slow): Critical user journeys through the real application
- Visual regression (targeted): Screenshot comparison for UI-heavy pages
What to Test at Each Layer
- Unit: Validation logic, formatters, reducers, computed values, utility functions
- Component: Rendering, user interactions, conditional UI, error states, loading states
- Integration: Form submissions, navigation flows, authenticated routes, data fetching
- E2E: Sign-up flow, checkout process, critical business workflows
Playwright
Setup and Configuration
- Install:
npm init playwright@latest - Configure
playwright.config.tswith multiple projects for cross-browser testing - Use
webServerconfig to auto-start your dev server before tests - Set
baseURLto avoid repeating full URLs in every test
Writing Effective Playwright Tests
// Use descriptive test names that explain the user journey
test('user can add item to cart and proceed to checkout', async ({ page }) => {
await page.goto('/products');
await page.getByRole('button', { name: 'Add to Cart' }).first().click();
await page.getByRole('link', { name: 'Cart' }).click();
await expect(page.getByText('1 item')).toBeVisible();
await page.getByRole('button', { name: 'Checkout' }).click();
await expect(page).toHaveURL(/.*checkout/);
});
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.
- 5d ago First seen · 177 lines · 24 tokens per session scan A 731e7d14196a
webapp-testing is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 1,935 once invoked, about $0.0001 per session on Opus 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
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
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.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…