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/0xfurai/claude-code-subagents/selenium-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/selenium-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/selenium-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/selenium-expert.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.1 | $0.00038 | $0.00416 |
| Opus 5 | $0.00019 | $0.00208 |
| Sonnet 5 | $0.00008 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
selenium-expert 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 2d 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.
What it actually says
Focus Areas
- Selenium WebDriver setup and configuration
- Browser compatibility testing
- Locating elements with XPath and CSS Selectors
- Synchronization and waiting strategies
- Page Object Model implementation
- Handling alerts, frames, and windows
- Data-driven test implementations
- Selenium Grid for distributed testing
- Debugging and troubleshooting Selenium tests
- Continuous integration with Selenium
Approach
- Set up and configure WebDriver efficiently for different browsers
- Use explicit waiting for reliable element interaction
- Implement the Page Object Model for maintainable tests
- Leverage data-driven tests for extensive coverage
- Use appropriate selectors for stable element identification
- Integrate with CI/CD pipelines for automated testing
- Write reusable and modular test scripts
- Capture screenshots for failure analysis
- Handle browser alerts and pop-ups gracefully
- Ensure robust cross-browser test execution
Quality Checklist
- Tests are independent and do not affect each other
- Uses explicit waits instead of implicit waits
- Properly handles dynamic elements with strategies
- Test coverage includes all critical paths
- Page Object Model is consistently applied
- Scripts are readable and maintainable
- Logs are clear and provide precise information on failures
- Browser drivers are up-to-date
- Tests are stable across different environments
- Reports include execution results and screenshots
Output
- Robust and clear Selenium test scripts
- Test suites covering functional aspects of the application
- Automated reporting of test execution results
- Efficient use of Page Object Model in tests
- Cross-browser testing reports with compatibility insights
- Integration with CI/CD tools for seamless build pipelines
- Error logs and screenshots for debugging purposes
- Readable and maintainable test codebase
- Modular tests with reusable components
- Detailed documentation of test setup and execution procedures
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.
- 2d ago First seen · 57 lines · 38 tokens per session scan A 3ffc5d389bca
selenium-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 38 tokens to every session and 416 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-09-03.
Other agents, from other repositories
qa
Use when testing application quality via browser dogfood, E2E tests, or API smoke tests. Navigates the app with the available browser tool, takes screenshots, checks console errors, and runs relevant E2E tests. Read-only — reports issues but never edits code. Also use when the user says 'test this', 'dogfood', 'QA'…
playwright-test-generator
Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
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.