Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSnpx agentmods add skills/dds-solutions/ai-tadpole-os/webapp-testingWrote 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/dds-solutions/ai-tadpole-os/webapp-testing)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/webapp-testing"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/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/dds-solutions/ai-tadpole-os/webapp-testing"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/webapp-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 54 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00020 | $0.00912 |
| Opus 5.5 | $0.00008 | $0.00365 |
| Sonnet 5.5 | $0.00004 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
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 3d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / webapp-testing
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Information drift, legacy terminology, or documentation mismatch.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Web Application Testing Protocol
Purpose: Systematic discovery, accessibility audit, and end-to-end verification of all web routes, user interactions, and UI components. Workflow Binding: Used directly during the
/testworkflow.
🎯 Progressive Disclosure & L3 Reference Index
Read REQUIRED testing rules below; consult deep L3 Reference Guides on demand:
| L3 Reference Guide / Tool | Purpose | Trigger / When to Load |
|---|---|---|
references/playwright_e2e_recipes.md |
Page Object Models, accessibility checks, screenshot diff fixtures | Writing Playwright test suites & UI flow automation |
scripts/playwright_runner.py |
Deterministic headless Playwright route runner & accessibility scanner | Automated E2E verification or --test validation |
🔍 1. Discovery-First Audit Strategy
1. MAP ROUTES ➔ Inspect React Router (`src/App.tsx`, `src/pages/`) and backend Axum endpoints.
2. HEALTH SCAN➔ Verify all primary routes mount without unhandled JavaScript exceptions.
3. FLOW TESTS ➔ Assert mission dispatch, vault unlocks, and task lifecycle events.
📐 2. Test Selection & Stability Guidelines
- Stable Selectors: Always use
data-testidor accessible ARIA roles (getByRole) rather than fragile CSS classes. - Auto-Waiting: Rely on Playwright built-in web-first assertions (
expect(locator).toBeVisible()). - State Isolation: Ensure each test starts with a clean or authenticated session state.
- Console Log Capture: Capture and fail on uncaught browser
window.onerroror unhandled promise rejections.
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.
- 3d ago Changed · +27 lines 0b0f5b659e5e
- 1mo ago First seen · 58 lines · 20 tokens per session scan A 2e25892341a4
webapp-testing is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 912 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-09-03.
Other skills, from other repositories
playwright-page-objects
Use when creating page objects or refactoring Playwright E2E tests for better maintainability with Page Object Model patterns.
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…
next-partial-prefetching-optimizer
Optimize what selected Next.js client navigations include before the click under Partial Prefetching. Use after Cache Components and Partial Prefetching are adopted when the user wants selected URL-specific UI to be instant, wants reusable content to wait for navigation, or needs to choose between default, viewport…
ux-acceptance-tester
Perform a goal-driven, black-box UX acceptance journey in a browser and report the path, friction, and observable outcome. Use only in an isolated tester context with a supplied start URL and brief.
ux-acceptance-coordinator
Coordinate black-box, agent-driven UX acceptance journeys against a disposable EmDash admin site. Use when preparing, dispatching, verifying, or reporting a manual browser journey performed by a separate tester agent. Do not use for deterministic Playwright tests or ordinary code review.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.