agent-browser
313Skill Claude CodeCodex
Browser automation CLI for AI agents. Use when you need to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, or testing web apps.
3,866 mods in this category, of every kind an agent can take. Each one carries what it costs per session, what the scan found, and whether it is the original.
Skill Claude CodeCodex
Browser automation CLI for AI agents. Use when you need to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, or testing web apps.
Plugin Claude Code
Bundles 2 skills, 1 hook · 304 tokens together
AI-powered testing for web and mobile apps. Find bugs by letting an AI agent explore your app like a real user.
Plugin Claude Code
Bundles 5 skills · 1,292 tokens together
Automated end-to-end testing toolkit for Shesha framework applications. Provides skills for scaffolding Playwright test infrastructure, authoring test plans, running tests locally and on remote hubs, and syncing results to a central reports dashboard.
Skill Codex
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.
Skill Claude CodeCodex
Show and maintain a discrete-node progress panel while ChatGPT uses its built-in browser for an authorized website acceptance test. Use when the user starts an @Browser acceptance task, asks to test a website with the in-app browser, or asks to show browser test progress. Do not use for ordinary browsing, research, or…
Skill Codex
A skill for creating, editing, checking, and diagnosing Russian-language Turbo Gherkin `.feature` files for Vanessa Automation, a tool for testing 1C applications. It covers UI and export scenarios without MCP.
Skill Claude Code
A guide for documenting and testing an existing software feature or page by studying how its code already works. It creates requirement, design, and test documents that describe the current behavior rather than an imagined future version.
GlamgarOnDiscord/claude-saas-blueprint
Skill Claude Code needs its repo
Tests E2E Playwright pour SaaS Next.js : setup, Page Object Model, auth state, flows critiques (login, billing, onboarding), CI GitHub Actions.
eliottvalette/Anthropic-Voodoo-Hackathon
Agent Claude Code
Headless browser tester and root-cause diagnostician for the proto-pipeline-m single-file HTML playables. Runs Playwright on the playable, captures the state trajectory and console errors, cross-references symptoms with the source sketches in 04sketches.json and the 04plan.json contract, and returns a structured…
Cursor rule Cursor
QA Recorder - Records user's manual browser interactions and generates natural language test scripts with rich locator metadata.
Skill Claude CodeCodex needs its repo
Write and review tests — unit, integration, and E2E — following the Testing Trophy model. Use after writing a feature, after fixing a bug (regression test required), during refactoring (existing tests must continue to pass), or during a quality audit to check overall coverage.
Skill Claude Code
Browser-based QA: exercises the running app via Playwright MCP, captures console errors and visual evidence, optionally fixes source bugs with atomic commits and generates regression tests. Three tiers (quick / standard / exhaustive). Writes uv-out/qa-state.md so /uvs-commit and /ship can detect completion and read…
Skill Claude CodeCodex
Use when Codex needs to run a local web app in a real browser, click/fill/press, wait for visible UI changes, save screenshots, and inspect console/page/request errors. Best default for browser smoke tests across repos.
Skill Claude CodeCodex
A browser-automation skill that uses ChromeDriver and Selenium to control a real Chrome browser for testing web pages.
Skill Claude CodeCodex
Playwright testing. Use this skill to write and run automated tests for web applications using Playwright.
Skill Claude Code
A workflow for end-to-end UI testing, which checks complete user journeys across a web application in a browser.
Kacper0199/Opencode-Ultrathinker
Skill Claude CodeCodex
End-to-end testing specialist using Playwright. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
Skill Claude Code
Automate browser interactions, test web pages and work with Playwright tests.
Plugin Claude Code
Bundles 2 skills, 1 agent · 202 tokens together
User Acceptance Testing workflow for web apps via Chrome DevTools MCP. Includes a setup skill for WSL2, a planning skill with auto-review, a tester skill with resume/abort semantics, and a structured bug-report format that hands off to a debugging agent.
Plugin Claude Code
Bundles 6 skills, 1 agent · 671 tokens together
AI-powered test generation skills for AWS Python projects — Lambda, API Gateway, Step Functions, and Batch. Generates E2E, integration, contract, performance, and load tests by reading actual handler code.
Plugin Claude Code
Bundles 4 skills, 4 commands, 1 agent · 369 tokens together
AI-driven Playwright test planning, generation, and self-healing — bring your own app profile.
Skill Claude CodeCodex
Use when iOS mobile E2E flows are flaky, SwiftUI and UIKit surfaces disagree with automation, mixed screens are ambiguous, retries hide the real issue, or the team keeps collapsing the problem to timing-only or SwiftUI-only without checking iOS-specific readiness contracts.
MCP server Claude CodeCodexCursor +2
MCP server for iOS Simulator control and browser automation - unified toolkit for mobile and web testing. Runs locally from the @plaintest/mcp-connect npm package.
MCP server Claude CodeCodexCursor +2
MCP server "playwright-pool-script" as configured in hy-2005/playwright-pool-mcp. Runs locally from the playwright-pool-script npm package.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: