interactive-live-testing

interactive-live-testing is a skill for Claude Code from mnzralee/claude-multi-agent-architecture. It costs 32 tokens per session (2,867 once invoked), scanned C, original, MIT.

A step-by-step testing guide that controls Playwright, a browser automation tool, against a running web application. It uses screenshots and observations to decide what to do next during testing.

In plain words
What is it for?
Use it to test web applications end to end, seed data through the interface, verify deployments, check authentication and forms, and investigate integration or visual bugs.
Why use it?
It catches problems that isolated unit tests may miss, such as broken login flows, form submissions, rendering, or connections between services. It also provides screenshot evidence for visual checks.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Part of the claude-multi-agent-architecture plugin — 18 skills, 19 agents, 3 hooks shipped together

Good fit Use it to test web applications end to end, seed data through the interface, verify deployments, check authentication and forms, and investigate integration or visual bugs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mnzralee/claude-multi-agent-architecture/interactive-live-testing
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.

Any agent
npx skills add mnzralee/claude-multi-agent-architecture --skill interactive-live-testing
Clone the repo
git clone --depth 1 https://github.com/mnzralee/claude-multi-agent-architecture

Made for: Claude Code.

Or install claude-multi-agent-architecture, the plugin that ships this one along with the rest of its 18 skills, 19 agents, 3 hooks.

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 interactive-live-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/mnzralee/claude-multi-agent-architecture/interactive-live-testing.svg)](https://agentmods.dev/skills/mnzralee/claude-multi-agent-architecture/interactive-live-testing)
Your own site
<a href="https://agentmods.dev/skills/mnzralee/claude-multi-agent-architecture/interactive-live-testing"><img src="https://agentmods.dev/badge/skills/mnzralee/claude-multi-agent-architecture/interactive-live-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,867 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.00032 $0.02867
Opus 5 $0.00016 $0.01434
Sonnet 5 $0.00006 $0.00573
Haiku 4.5 $0.00003 $0.00287

Measured 8d ago against content hash c98b4b6347c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade C, and why

interactive-live-testing scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

| Turbopack or Webpack stale cache | Old component renders after a fix | `rm -rf .next` (or `dist/`) and restart the dev server |
.claude/skills/interactive-live-testing/SKILL.md · 315 lines

How it starts

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

Interactive Live Testing Skill

Drive Playwright against a running application step-by-step, screenshot, analyze, decide, act. Like a senior QA engineer manually testing but with full programmatic control. The discipline is stack-agnostic and applies to any web frontend (Next.js, Vite, Create React App, Vue, Angular, or similar).

When to Use

  • Seeding data through actual UI flows rather than API shortcuts
  • Verifying end-to-end rendering after a deployment or build
  • Finding integration bugs that unit tests miss
  • Visual regression testing with screenshot evidence
  • Testing auth flows, form submissions, and event-driven pipelines live

Philosophy

See, Decide, Act, Verify. Never script 50 steps blind. Take a screenshot, read it, decide the next action based on what you SEE. Every bug found is fixed immediately, committed, rebuilt, and retested before proceeding.

Prerequisites

Before any live testing session:

# 1. Verify services are running (adapt to your runtime: Docker Compose, k8s, PM2, etc.)
#    [CUSTOMIZE: replace with your health-check command]
docker compose ps   # or: kubectl get pods -n [CUSTOMIZE: namespace]

# 2. Expose required services on localhost if behind a proxy or cluster
#    [CUSTOMIZE: port-forward, ngrok tunnel, or docker compose ports mapping]
kubectl port-forward deploy/svc-api 3001:3001 &
kubectl port-forward deploy/svc-auth 3002:3002 &

# 3. Start the frontend locally (or confirm the dev server is already running)
#    [CUSTOMIZE: your frontend start command and environment variables]
cd apps/web && NEXT_PUBLIC_API_URL=http://localhost:3001 npm run dev

# 4. Verify Playwright is installed in the frontend package
cd apps/web && npx playwright install chromium

Core Pattern: Step-by-Step Navigation

Always run Playwright from the directory where it is installed (the frontend app package):

cd /path/to/your/apps/web && node -e "
const { chromium } = require('playwright');
(async () => {
  const browser = await chromium.launch({ headless: true });
  const page = await browser.newPage({ viewport: { width: 1440, height: 900 } });

  // --- YOUR ACTIONS HERE ---
  await page.goto('http://localhost:3000/...', { waitUntil: 'networkidle', timeout: 30000 }).catch(() => {});
  await page.waitForTimeout(2000);

  // --- SCREENSHOT ---
  await page.screenshot({ path: '/tmp/playwright-live-test/XX-description.png', fullPage: true });

  // --- ANALYZE ---
  const body = await page.textContent('body');
  console.log('Has expected text:', body.includes('Expected'));

  await browser.close();
})();
" 2>&1

Read the full file on GitHub · 315 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. 8d ago First seen · 315 lines · 32 tokens per session scan C c98b4b6347c7

Subscribe to this mod's changes

interactive-live-testing is a skill published in the GitHub repository mnzralee/claude-multi-agent-architecture (5 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 2,867 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

test-engineer

Automated E2E testing with Playwright including the auto-fix loop — generate test cases from the UI, run them, fix failures and re-run until passing, then produce a human-readable report. Test until it passes, not just test and report. Drives /toh-test; use whenever tests must be written, run, or made green.

wasintoh/toh-framework · 75 tokens

browser-automation

Local Python-based browser automation toolkit using Playwright. Provides command-line tools for navigating, interacting with, and testing web applications without using MCP protocols. Supports clicking, typing, hovering, screenshots, content extraction, and JavaScript execution.

archubbuck/workspace-architect · 50 tokens

browser-automation

Browser automation powers web testing, scraping, and AI agent.

hybridlabor-api/bdb-dev-optimized-agent-skills · 15 tokens

dev-browser

CIEL's framework for browser automation with persistent page state. Navigates URLs, fills forms, takes screenshots, scrapes data, and tests web apps via sandboxed JavaScript scripts.

jxoesneon/Ciel · 40 tokens

deckforge-visual-evidence

Start a DeckForge application in an isolated browser session, exercise editor/presenter/viewer/export capabilities, capture screenshots, console errors, failed requests, accessibility results, and traces, generate machine-readable evidence, and stop every process the run created. Use for visual QA of generated…

tph-kds/deckforge · 71 tokens

e2e-and-visual-verification

CIEL's framework for Playwright E2E testing and intentional frontend design.

jxoesneon/Ciel · 25 tokens