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 agentmods add skills/timothywarner/copilot-dev/webapp-testingnpx skills add timothywarner/copilot-dev --skill webapp-testinggit clone --depth 1 https://github.com/timothywarner/copilot-devWhat 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 | $0.00071 | $0.01857 |
| Opus 5 | $0.00036 | $0.00928 |
| Sonnet 5 | $0.00014 | $0.00371 |
| Haiku 4.5 | $0.00007 | $0.00186 |
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 2d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webapp Testing Skill
You are an expert in writing E2E and component tests for web applications using Playwright (for browser-based tests) and Jest + Testing Library (for component/unit tests). When this skill is active, follow every step below precisely.
Step 1: Identify the Target File and Testable Flows
Before writing a single line of test code:
- Read the target HTML, component, or route file completely.
- Enumerate every user flow visible in the UI:
- Form submissions (login, register, search, checkout)
- Navigation (links, breadcrumbs, tabs, modals)
- State changes (error messages, success banners, loading spinners)
- Authentication gates (redirect to login, session expiry)
- Prioritize flows by risk: authentication > data mutation > read-only display.
- Ask yourself: "If this flow broke silently in production, what would users notice first?" — test that first.
Step 2: Choose the Right Test Type
| Scenario | Test Type | Tool |
|---|---|---|
| Full browser flow (login → dashboard) | E2E | Playwright |
| Single component rendering | Component | Jest + Testing Library |
| API response handling in UI | Integration | Playwright with mock routes |
| Accessibility | A11y | Playwright + axe-core |
Step 3: Selector Strategy (Accessibility-First)
Always prefer selectors in this order:
// 1. BEST: Role + accessible name (resilient to CSS/layout changes)
await page.getByRole('button', { name: 'Sign in' }).click();
await page.getByRole('textbox', { name: 'Email address' }).fill('[email protected]');
// 2. GOOD: Label text (tied to semantic HTML)
await page.getByLabel('Password').fill('secret');
// 3. OK: Placeholder text (only if no label exists)
await page.getByPlaceholder('Enter your email').fill('[email protected]');
// 4. LAST RESORT: data-testid (when no semantic option exists)
await page.getByTestId('submit-btn').click();
// NEVER USE: CSS class names, XPath, positional selectors
// BAD:
await page.locator('.btn-primary').click(); // breaks on CSS refactor
await page.locator('//button[1]').click(); // brittle, breaks on DOM changes
What ships with it
2 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.
- 2d ago First seen · 210 lines · 71 tokens per session scan A 77feb1328df7
webapp-testing is a skill published in the GitHub repository timothywarner/copilot-dev (46 stars, last pushed 29d ago), licensed MIT. It adds 71 tokens to every session and 1,857 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…