ac-qa-test-e2e

ac-qa-test-e2e is a skill for Claude Code from WaterplanAI/agentic-config. It costs 49 tokens per session (803 once invoked), scanned A, original, MIT.

An end-to-end test runner that reads test steps from a definition file and carries them out in a browser using Playwright. End-to-end tests check an application through the same kind of interactions a user makes.

In plain words
What is it for?
Use it to test a running web app by navigating, filling fields, clicking controls, checking results, and capturing evidence.
Why use it?
It turns written test scenarios into repeatable browser checks and records screenshots during the run.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Part of the agentic-config plugin — 49 skills, 1 plugin shipped together

Install

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.

agentmods
npx agentmods add skills/waterplanai/agentic-config/ac-qa-test-e2e
Any agent
npx skills add WaterplanAI/agentic-config --skill ac-qa-test-e2e
Clone the repo
git clone --depth 1 https://github.com/WaterplanAI/agentic-config

Made for: Claude Code.

Or install agentic-config, the plugin that ships this one along with the rest of its 49 skills, 1 plugin.

Wrote 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.

agentmods badge for ac-qa-test-e2e

README.md
[![agentmods](https://agentmods.dev/badge/skills/waterplanai/agentic-config/ac-qa-test-e2e.svg)](https://agentmods.dev/skills/waterplanai/agentic-config/ac-qa-test-e2e)
Your own site
<a href="https://agentmods.dev/skills/waterplanai/agentic-config/ac-qa-test-e2e"><img src="https://agentmods.dev/badge/skills/waterplanai/agentic-config/ac-qa-test-e2e.svg" alt="Measured on agentmods" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 803 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.00803
Opus 5 $0.00024 $0.00402
Sonnet 5 $0.00010 $0.00161
Haiku 4.5 $0.00005 $0.00080

Measured 6d ago against content hash 5c7c3302e381, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

ac-qa-test-e2e 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 6d 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.

packages/pi-ac-qa/skills/ac-qa-test-e2e/SKILL.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

E2E Test Runner

Execute E2E test steps from a test definition file.

Test File: $1 Base URL: $2 (default: http://localhost:${DEFAULT_PORT:-5173}/)

Pre-Flight Checks

  1. Verify Test File Exists

    • Read test file from $1
    • If not found: STOP with "Test file not found: $1"
  2. Verify playwright-cli Installed

    • Run: playwright-cli --help
    • If not available: STOP with "playwright-cli not installed. Run: npm install -g @playwright/cli@latest"
  3. Parse Test Definition

    • Extract: Test Name, User Story, Test Steps, Success Criteria
    • If parsing fails: STOP with parse error details

Execution

  1. Initialize Test Session

    • Record test start timestamp
    • Create screenshot directory: {PROJECT_ROOT}/outputs/e2e/<test-name>/
  2. Navigate to Base URL

    • Run: playwright-cli open <base_url>
    • Run: playwright-cli screenshot --output {PROJECT_ROOT}/outputs/e2e/<test-name>/01_initial.png
  3. Execute Test Steps

    • For each step in Test Steps section: a. Parse step action (Navigate, Verify, Click, Fill, Type, Screenshot) b. Execute action using appropriate playwright-cli command:
      • Navigate: playwright-cli goto <url>; Verify: playwright-cli snapshot; Click: playwright-cli click "<selector>"; Fill: playwright-cli fill "<selector>" "<text>"; Screenshot: playwright-cli screenshot --output <path> c. If step includes "screenshot": capture and save d. If step includes "verify": validate condition e. On failure: record error and continue to capture state
  4. Validate Success Criteria

    • Check each criterion from Success Criteria section
    • Mark as passed/failed
  5. Generate Result JSON

    • Output structured result to stdout

Output Format

Return JSON result:

{
  "test_name": "<name from test file>",
  "status": "passed|failed",
  "timestamp": "<ISO timestamp>",
  "duration_ms": <number>,
  "steps": [
    {"step": 1, "action": "navigate", "status": "passed"},
    {"step": 2, "action": "verify", "status": "passed"}
  ],
  "screenshots": [
    "{PROJECT_ROOT}/outputs/e2e/<test-name>/01_initial.png"
  ],
  "video": "{PROJECT_ROOT}/outputs/e2e/<timestamp>-<test-name>.webm",
  "error": null
}

Read the full file on GitHub · 93 lines

Changes

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.

  1. 6d ago First seen · 93 lines · 49 tokens per session scan A 5c7c3302e381

Subscribe to this mod's changes

ac-qa-test-e2e is a skill published in the GitHub repository WaterplanAI/agentic-config (30 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 803 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

selectors

Selector strategy, exploration-first workflow, locator priority order (getByRole then getByLabel then getByPlaceholder then getByText then getByTestId), and feedback/validation-message selector rules for Playwright page objects. Use when creating page objects, writing or updating locators, generating UI tests, or…

idavidov13/agentic-playwright · 136 tokens

vindicate

Use when the user wants to write, add, fix, stabilize (flaky), refactor, run, or audit Playwright browser tests, draft requirements/stories from a recording (no tests), find test-coverage gaps, scaffold a Playwright project, or set up Playwright CI. Vindicate's guided workflow for grounded, conformant Playwright test…

OpenEvident/vindicate · 77 tokens

playwright-browser-automation

Run automated headless browser testing, scrape dynamic SPAs, capture high-resolution full-page screenshots, and perform visual regression testing with Playwright.

pedroiff0/awesome-skills · 34 tokens

playwright-cli

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

idavidov13/agentic-playwright · 52 tokens

e2e-testing-patterns

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

wshobson/agents · 51 tokens

browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…

addyosmani/agent-skills · 68 tokens