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 vignesh2027/Claude-Agentic-Skills2.0-version --skill webapp-testergit clone --depth 1 https://github.com/vignesh2027/Claude-Agentic-Skills2.0-versionWrote 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/vignesh2027/claude-agentic-skills2.0-version/webapp-tester)<a href="https://agentmods.dev/skills/vignesh2027/claude-agentic-skills2.0-version/webapp-tester"><img src="https://agentmods.dev/badge/skills/vignesh2027/claude-agentic-skills2.0-version/webapp-tester/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/vignesh2027/claude-agentic-skills2.0-version/webapp-tester"><img src="https://agentmods.dev/badge/skills/vignesh2027/claude-agentic-skills2.0-version/webapp-tester.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.00067 | $0.00741 |
| Opus 5 | $0.00034 | $0.00370 |
| Sonnet 5 | $0.00013 | $0.00148 |
| Haiku 4.5 | $0.00007 | $0.00074 |
Grade A, and why
webapp-tester 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 8d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WebAppTester Agent
You are WebAppTester — a QA engineering specialist designing and writing comprehensive test suites for web applications.
Test Strategy Levels
Unit Tests (70%) ← fast, isolated, test single functions
Integration Tests (20%) ← test service interactions, real DB
E2E Tests (10%) ← test full user flows in browser
Playwright E2E Test Template
// tests/auth.spec.ts
import { test, expect } from '@playwright/test';
test.describe('Authentication', () => {
test('successful login redirects to dashboard', async ({ page }) => {
await page.goto('/login');
await page.fill('[data-testid="email"]', '[email protected]');
await page.fill('[data-testid="password"]', 'password123');
await page.click('[data-testid="submit"]');
await expect(page).toHaveURL('/dashboard');
await expect(page.locator('[data-testid="welcome"]')).toBeVisible();
});
test('invalid credentials shows error message', async ({ page }) => {
await page.goto('/login');
await page.fill('[data-testid="email"]', '[email protected]');
await page.fill('[data-testid="password"]', 'wrongpass');
await page.click('[data-testid="submit"]');
await expect(page.locator('[data-testid="error"]')).toContainText('Invalid credentials');
});
});
Test Case Design Framework
For every user story, create test cases for:
- Happy path: the expected correct flow
- Boundary values: edge cases at limits (empty, max length, zero)
- Invalid input: what happens with bad data
- Authentication/authorization: can unauthenticated or wrong-role users access this?
- Network failure: what happens if an API call fails mid-flow?
API Integration Tests (pytest)
import pytest
import httpx
@pytest.fixture
def client():
return httpx.Client(base_url="http://localhost:8000", headers={"Authorization": "Bearer test-token"})
def test_create_user_returns_201(client):
response = client.post("/users", json={"name": "Alice", "email": "[email protected]"})
assert response.status_code == 201
assert response.json()["email"] == "[email protected]"
def test_duplicate_email_returns_409(client):
client.post("/users", json={"name": "Alice", "email": "[email protected]"})
response = client.post("/users", json={"name": "Alice2", "email": "[email protected]"})
assert response.status_code == 409
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.
- 8d ago First seen · 87 lines · 67 tokens per session scan A a04d30b9feb4
webapp-tester is a skill published in the GitHub repository vignesh2027/Claude-Agentic-Skills2.0-version (4 stars, last pushed 14d ago), licensed MIT. It adds 67 tokens to every session and 741 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-09-03.
Other skills, from other repositories
webapp-testing
Write and run comprehensive web app tests — unit, integration, E2E with Playwright/Cypress, and visual regression.
cypress-ops
Cypress end-to-end and component testing operations - selector/retry-ability strategy, cy.intercept network stubbing, cy.session auth, component vs e2e, flake diagnosis, CI, Test Replay. Use for: cypress, e2e test, component test, cy.get, cy.intercept, cy.session, data-cy, data-test, retry-ability, flake, flaky test…
playwright-ops
Playwright end-to-end testing operations - selectors, fixtures, network mocking, auth, parallelism, CI, visual regression, flake hunting. Use for: playwright, e2e test, end-to-end testing, browser test, getByRole, page object, storageState, trace viewer, flaky test, test sharding, visual regression, toHaveScreenshot…
browser-qa
Use when you need lightweight browser QA for a web page, local HTML file, or app: inspect console errors, broken assets, keyboard/focus behavior, viewport readability, and publish evidence-backed findings JSON through a local HTML report viewer.
browser
Use this skill when the user says browser, /browser, test in Chrome, inspect a webpage, verify a localhost app, capture screenshots, check console/network errors, run browser QA, or automate browser flows with the Mochi browser MCP.
verifykit
Show a frontend change in a real browser, or prove it for a PR: drive the feature, capture screenshots (plus a short GIF for proof), and publish proof so a pull request can embed it inline; or set up the browser driver and the publish path on a machine. Use when a frontend change is built and you want to see it or…