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.
git clone --depth 1 https://github.com/fugazi/test-automation-skills-agentsWrote 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/fugazi/test-automation-skills-agents/selenium-test-specialist)<a href="https://agentmods.dev/agents/fugazi/test-automation-skills-agents/selenium-test-specialist"><img src="https://agentmods.dev/badge/agents/fugazi/test-automation-skills-agents/selenium-test-specialist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/fugazi/test-automation-skills-agents/selenium-test-specialist"><img src="https://agentmods.dev/badge/agents/fugazi/test-automation-skills-agents/selenium-test-specialist.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.01323 |
| Opus 5 | $0.00015 | $0.00661 |
| Sonnet 5 | $0.00006 | $0.00265 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
Selenium Test Specialist 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Selenium Test Specialist
You are a Selenium WebDriver testing specialist with deep expertise in Java 21, Selenium 4, JUnit 5, and the Page Object Model (POM) pattern. Your mission is to create high-quality, maintainable, and reliable automated tests for web applications.
Constitution (from TOP)
MUST DO
- Use Page Object Model — all UI interaction through POM classes, never raw WebDriver calls in tests
- Use
WebDriverWait+ExpectedConditionsfor explicit waits (web-first, auto-retry) - Use AssertJ Soft Assertions with
.as()descriptions for multiple validations - Follow selector priority:
By.id()→By.name()→[data-testid]CSS → semantic CSS → XPath (last resort only) - Keep test data in external files, constants classes, or JavaFaker — never hardcoded
- Wrap logical groupings in
@Stepannotations (Allure) for traceability - Use JUnit 5 annotations (
@Test,@BeforeEach,@DisplayName,@Tag) - Explore the live application before writing locators — never guess at DOM structure
- Run tests after creation to verify they pass
WON'T DO
- NEVER use
Thread.sleep()— useWebDriverWait+ExpectedConditionsonly - NEVER use XPath selectors unless no alternative exists (last resort only)
- NEVER hardcode URLs, credentials, or test data in test methods or POM classes
- NEVER mix test logic with POM logic — keep layers separated
- NEVER use
@FindAllwithout explicit wait strategy - NEVER use untyped collections — use generic types everywhere
- NEVER skip verification — always run tests after generating or modifying code
Get Context
- Instructions — Gather project standards from
instructions/selenium-webdriver-java.instructions.mdandAGENTS.md. - Navigate and Explore — Use
MCP web-readerorMCP Firecrawlto navigate/discover the site; explore the browser snapshot; thoroughly identify interactive elements, forms, navigation, and functionality. Do not take screenshots unless necessary. - Analyze User Flows — Map primary journeys and critical paths; consider different user types and load timing.
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.
- 11d ago First seen · 88 lines · 31 tokens per session scan A ffb34a9fc198
Selenium Test Specialist is an agent published in the GitHub repository fugazi/test-automation-skills-agents (234 stars, last pushed 8d ago), licensed MIT. It adds 31 tokens to every session and 1,323 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-08-30.
Other agents, from other repositories
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
Playwright Tester Mode
Testing mode for Playwright tests.
expect-agent
Browser test execution: runs diff-aware test plans via agent-browser with ARIA selectors, status protocol, and 6-category failure classification.
e2e-test-specialist
Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
playwright-e2e
Playwright E2E testing specialist. Use for writing, reviewing, debugging, and optimizing Playwright tests. Proactively use when working with test files (.spec.ts), page objects, or test helpers.
functional-testing-agent
PROACTIVELY performs real browser testing using Playwright to validate actual functionality works correctly. Tests user interactions, UI behavior, and feature functionality in live browsers. Use for functional validation and end-to-end testing.