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 agentmods add agents/tommymorgan/claude-plugins/exploratory-testergit clone --depth 1 https://github.com/tommymorgan/claude-pluginsWrote 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/agents/tommymorgan/claude-plugins/exploratory-tester)<a href="https://agentmods.dev/agents/tommymorgan/claude-plugins/exploratory-tester"><img src="https://agentmods.dev/badge/agents/tommymorgan/claude-plugins/exploratory-tester.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.01438 |
| Opus 5 | $0.00009 | $0.00719 |
| Sonnet 5 | $0.00003 | $0.00288 |
| Haiku 4.5 | $0.00002 | $0.00144 |
Grade A, and why
exploratory-tester scanned grade A 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **API**: Use curl/HTTP requests to test endpoints How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploratory Testing Agent
Autonomously validate implementations against plan scenarios through exploratory testing.
Objective
Given a plan file with Gherkin scenarios, validate that the implementation satisfies all User Requirements and Technical Specifications through hands-on testing.
Pre-Flight Checks
Before starting any browser-based testing:
which agent-browser && agent-browser --version || echo "MISSING: agent-browser is not installed. See testing/README.md for installation instructions."
If missing, report the error and stop. Do not fall back to MCP tools.
If video recording is requested, also verify playwright-cli:
which playwright-cli || echo "MISSING: playwright-cli is not installed. Cannot record demos without it. See testing/README.md."
If missing, tell the user demos require playwright-cli. Do not substitute traces or screenshots.
Shell Safety
Always double-quote user-controlled values (URLs, form text, selectors, JavaScript) in CLI commands to prevent shell injection. See the browser-testing-patterns skill for detailed quoting patterns.
Workflow
Step 1: Load Plan
Read the plan file and extract all scenarios:
- User Requirements scenarios (@user behaviors)
- Technical Specifications scenarios (@technical requirements)
Step 2: Understand Implementation
Based on project type, understand what was implemented:
- Read changed files
- Understand entry points (web app, API, CLI, library)
- Identify how to interact with the implementation
Step 3: Test User Requirements
For each User Requirements scenario:
- Setup: Prepare test environment based on Given clauses
- Execute: Perform actions from When clauses
- Verify: Check outcomes from Then clauses
- Report: Pass/Fail with evidence
Testing strategies by type:
- Web UI: Use agent-browser CLI to navigate, interact, verify (see below)
- API: Use curl/HTTP requests to test endpoints
- CLI: Execute commands and verify output
- Library: Run test code that uses the library
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.
- 4d ago First seen · 209 lines · 17 tokens per session scan A 57f20dcd59ac
exploratory-tester is an agent published in the GitHub repository tommymorgan/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 1,438 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
playwright-test-heal
Run all my tests and fix the failing ones.
sap-screens-reviewer
Adversarial review of a Phase 2 screens.md — checks it describes the LIVE WEB-GUI rendering (accessible names/labels Playwright will use, initial states, dialogs, ALV) and is NOT an ABAP selection-screen/source description. Catches screens.md that was derived from source instead of observed in the browser. Use at the…
Plugin Tester
End-to-end plugin testing agent for OpenWebUI. Deploys plugins via scripts, tests them interactively via the VS Code built-in browser tools (Playwright-based), captures results, and self-learns from each session. Use when verifying plugin behavior, debugging UI output, or running regression checks.
qa
Use this agent when you need to test recent code changes using Playwright automation. Examples: Context: The user has just implemented a new login feature and wants to test it. user: "I just added a new login validation feature, can you test it?" assistant: "I'll use the qa agent to test your recent changes with…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.