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/code-saurabh/openskills/webapp-testingnpx skills add CODE-SAURABH/OpenSkills --skill webapp-testinggit clone --depth 1 https://github.com/CODE-SAURABH/OpenSkillsWhat 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.00068 | $0.02917 |
| Opus 5 | $0.00034 | $0.01458 |
| Sonnet 5 | $0.00014 | $0.00583 |
| Haiku 4.5 | $0.00007 | $0.00292 |
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 yesterday.
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 — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web App Testing (Playwright)
Manual testing finds bugs once. Automated tests find them every time. This skill writes Playwright scripts that test real browser behaviour — clicks, forms, navigation, network calls, and visual state — reliably and repeatably.
Web App Testing Principles
- Reconnaissance before action. Never assume a selector exists. Navigate, wait for load, inspect the DOM, then act. Selectors that work in dev break in staging. Discover them at runtime.
- Wait for real readiness.
networkidleis not always enough. Wait for the specific element you need, not just page load. - Test what the user experiences. Test by role, text, and label — not by CSS class or XPath. Classes change; user-facing text is more stable.
- One test, one user journey. A test that does login + checkout + confirmation + email verification is four tests jammed together. Split them.
- Tests must clean up after themselves. A test that leaves state (created users, placed orders) that affects the next test is a flaky test waiting to happen.
- Screenshot on failure. Every test should capture a screenshot when it fails — this is the single fastest debugging tool available.
Step 0: Choose the Right Approach
Is the app running?
├── NO → Start it first with with_server.py helper (if available)
│ or: npm run dev / python app.py in background
└── YES
└── Is it static HTML (no JS framework)?
├── YES → Read HTML directly, write selectors from source
└── NO (React, Vue, Svelte, etc.)
→ Reconnaissance first: navigate → networkidle → screenshot → inspect → act
Project Setup
Install Playwright
npm init -y
npm install -D @playwright/test
npx playwright install chromium # or: install firefox, webkit too
# Python
pip install playwright
playwright install chromium
Config (playwright.config.ts)
import { defineConfig } from "@playwright/test";
export default defineConfig({
testDir: "./tests",
timeout: 30_000,
retries: process.env.CI ? 2 : 0, // retry in CI, not locally
use: {
baseURL: process.env.BASE_URL ?? "http://localhost:3000",
headless: true,
screenshot: "only-on-failure", // always capture on failure
video: "retain-on-failure",
trace: "retain-on-failure",
},
webServer: {
command: "npm run dev",
port: 3000,
reuseExistingServer: !process.env.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.
- yesterday First seen · 382 lines · 68 tokens per session scan A 62f4cb0c65c4
webapp-testing is a skill published in the GitHub repository CODE-SAURABH/OpenSkills (2 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 2,917 once invoked, about $0.0003 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-31.
Other skills, from other repositories
agent-framework-azure-ai-py
Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
aria
Designs the data model, API contracts, and structural foundation of the system.
accint-commitments
Triage acc's open promises and close them with honest real-world verdicts via accact(runtime="outcome").
ecommerce-landing-page
Audit and optimize e-commerce landing pages for conversion. CTA placement, trust signals, page structure, copy optimization, and A/B testing strategy for product pages, collection pages, and campaign landing pages.
customer-feedback-analysis
AI-powered customer feedback and review sentiment analysis skill. Extracts pain points, feature requests, and improvement priorities from customer reviews across e-commerce platforms.
ads-linkedin
Audit LinkedIn Ads measurement, Insight Tag and conversions, professional audiences, lead generation, ABM, creative, bidding, budgets, pacing, automation, and policy. Use for LinkedIn Ads, Campaign Manager, Insight Tag, Lead Gen Forms, Thought Leader Ads, ABM campaigns, or B2B paid media.