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 JNZader/repoforge --skill webapp-testinggit clone --depth 1 https://github.com/JNZader/repoforgeWrote 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/jnzader/repoforge/webapp-testing)<a href="https://agentmods.dev/skills/jnzader/repoforge/webapp-testing"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/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/jnzader/repoforge/webapp-testing"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/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.00049 | $0.00724 |
| Opus 5.5 | $0.00020 | $0.00290 |
| Sonnet 5.5 | $0.00010 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00072 |
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Patterns for browser-based UI verification using Playwright. Reliable, maintainable, fast E2E tests.
Selector Priority
| Priority | Selector | Example | Why |
|---|---|---|---|
| 1 | Role | getByRole('button', { name: 'Submit' }) |
Accessible, semantic |
| 2 | Label | getByLabel('Email') |
Accessible, user-facing |
| 3 | Test ID | getByTestId('submit-btn') |
Stable, explicit |
| 4 | Text | getByText('Sign in') |
Readable but fragile |
| 5 | CSS | page.locator('.btn-primary') |
Last resort |
NEVER: XPath, auto-generated IDs, DOM structure selectors.
Page Object Model
export class LoginPage {
constructor(private page: Page) {}
get emailInput() { return this.page.getByLabel('Email'); }
get passwordInput() { return this.page.getByLabel('Password'); }
get submitButton() { return this.page.getByRole('button', { name: 'Sign in' }); }
async login(email: string, password: string) {
await this.emailInput.fill(email);
await this.passwordInput.fill(password);
await this.submitButton.click();
}
}
Visual Regression
test('dashboard renders correctly', async ({ page }) => {
await page.goto('/dashboard');
await page.waitForLoadState('networkidle');
await expect(page).toHaveScreenshot('dashboard.png', { maxDiffPixelRatio: 0.01 });
});
Network Interception
test('handles API errors', async ({ page }) => {
await page.route('**/api/users', route =>
route.fulfill({ status: 500, body: 'Server Error' })
);
await page.goto('/users');
await expect(page.getByText('Something went wrong')).toBeVisible();
});
Anti-Flakiness
- Wait for state, not time — never
page.waitForTimeout() - Isolate tests — fresh context per test
- Web-first assertions —
expect(locator).toBeVisible()auto-retries - Mock external APIs
- CI retries:
retries: 2in config
Critical Rules
- NEVER use
page.waitForTimeout()— wait for specific conditions - ALWAYS use Page Object Model for pages with 3+ interactions
- Selectors MUST follow priority: role > label > testid > text > CSS
- Visual regression MUST set
maxDiffPixelRatio - E2E tests MUST NOT depend on seed data
- ALWAYS use
--trace on-first-retryin CI
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 · 100 lines · 49 tokens per session scan A 2dba5753b866
webapp-testing is a skill published in the GitHub repository JNZader/repoforge (5 stars, last pushed 24d ago), licensed MIT. It adds 49 tokens to every session and 724 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-08-31.
Other skills, from other repositories
browser-qa
Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console errors and screenshot evidence. Use on a web surface end to end, or to reproduce a front-end bug.
browser-qa
QA de navegador y regresión visual con Playwright: navegación, capturas (viewport/página/elemento), comparación contra baseline, snapshots de accesibilidad e inspección de red/consola/DOM, cross-browser.
automated-web-interactive-bug-reporting
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
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.
dogfood
Exploratory QA of web apps: find bugs, evidence, reports.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.