5,255 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.
AGENTS.md instructions for mdsohaib/screenshot-time-machine, covering agents.md: how to work in this repo (humans and ai agents), setup (5 commands), module map (v0.1), hard rules (a pr that breaks one will be closed) and before you open a pr.
Run an isolated persona-based UX test through the real desktop or browser UI. Creates a precise non-developer user persona, gives the tester only an approved product introduction, prevents source-code and design-document leakage, and produces an evidence-based Chinese evaluation report. Use when the user asks for…
Add a new browser tool to the Chrome Bridge end to end — MCP tool in server/index.js, handler in extension/background.js, e2e assertion, README row. Use when asked to add, rename, or remove a browser capability exposed to Claude Code.
Where WeftCut's tests live, why they're split the way they are, and how to run each layer. There is no single tests/ directory — that's deliberate (see Why not one directory). Tests are grouped by runner, not scattered by neglect.
A test-building tool for generating several kinds of checks for code. It covers static analysis, which examines code without running it, plus unit, integration, and end-to-end tests and coverage reports.
Domain skill - run screenshot-light PIE playtest episodes with structured entity observations, bounded semantic actions, transition polling, and in-memory traces for QA and external policy or RL runners.
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.
QA artifact generator — point it at a PR or give freeform instructions. Navigates the UI, captures screenshots, and stitches a GIF. Fully configurable auth and artifact storage via /.sentinel/config.json.
★not rated 4 2mo agoA
tokens not measured
originalMIT
MCP server "playwright-test-generator-mcp" as configured in ingpoc/ui-test-generation-mcp. Runs locally from the playwright-test-generator-mcp npm package.
Podium — the mobile + canvas automation MCP for AI agents: iOS & Android control, native UI automation, Maestro E2E, React Native debugging, and a no-vision canvas/WebGL brain that taps game UIs like DOM elements — for Claude Code.
★not rated 4 2mo agoA
tokens not measured
originalMIT
Validate UIs by clicking through them like a real user — iOS Simulator, Android emulator, tvOS, desktop, and web. Detects the platform and picks the right tool — agent-device (Callstack) for mobile/TV/desktop, agent-browser (Vercel Labs) for web, Maestro + Maestro Viewer for declarative cross-platform flows; raw xcrun…
A workflow that reviews code changes and suggests mutation tests or end-to-end tests. Mutation testing changes code deliberately to see whether tests detect the change, while end-to-end testing checks a complete user flow.
Self-healing QA agent for copilot-engine. Checks prerequisites, build, server health, and API smoke tests. Auto-fixes what it can before reporting issues.
Instructions for fastslack/mtw-e2e-runner, covering claude.md, project overview, commands, install dependencies and scaffold e2e/ directory in a consuming project.
A test-suite generation workflow for software projects. It includes static checks, unit tests, integration tests, end-to-end tests, coverage reports, type checking, linting, security scanning, and dead-code detection.
Instructions for willbytee-sudo/android-qa-kit, covering agents.md — setting up and driving an android device, 1. how to work with the user, 2. start by finding out what's already there, 3. what you can do in each mode and 4. if there's no device: ask first.
Use when completion depends on an end-to-end outcome across components, environments, or external systems.
★not rated 3 1mo agoA23 tokens
originalMIT
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: