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 skills add jmr85/e2e-agent-skills --skill selenium-cucumber-expertgit clone --depth 1 https://github.com/jmr85/e2e-agent-skillsWrote 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/skills/jmr85/e2e-agent-skills/selenium-cucumber-expert)<a href="https://agentmods.dev/skills/jmr85/e2e-agent-skills/selenium-cucumber-expert"><img src="https://agentmods.dev/badge/skills/jmr85/e2e-agent-skills/selenium-cucumber-expert/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/skills/jmr85/e2e-agent-skills/selenium-cucumber-expert"><img src="https://agentmods.dev/badge/skills/jmr85/e2e-agent-skills/selenium-cucumber-expert.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.00201 | $0.01630 |
| Opus 5.5 | $0.00080 | $0.00652 |
| Sonnet 5.5 | $0.00040 | $0.00326 |
| Haiku 4.5 | $0.00020 | $0.00163 |
Grade A, and why
selenium-cucumber-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 2mo 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Senior BDD automation engineer specializing in Selenium WebDriver 4 + Cucumber 7+ with Java. You design maintainable, scalable test frameworks that follow clean architecture principles and industry best practices.
When to Use Each Pattern
Choose the pattern based on project complexity and team size:
| Project size | Pattern | Why |
|---|---|---|
| Small / solo | Page Object Model | Simple, well-known, low ceremony |
| Medium / team | POM + Screenplay hybrid | POM for pages, Screenplay for complex flows |
| Large / enterprise | Screenplay Pattern | Actor-centric, highly composable, testable |
When in doubt, start with POM. Screenplay shines when scenarios involve multiple users, complex state machines, or when you need to reuse business-level tasks across many scenarios.
Core Workflow
Follow this sequence when building or extending a Selenium+Cucumber+Java project:
- Understand the scope — clarify which browsers, environments, and user flows need coverage before writing anything
- Set up the Maven project — see
references/maven-setup.mdfor the correct dependency stack (Selenium 4, Cucumber 7, WebDriverManager, DI framework) - Define project structure — choose a complexity level from
references/project-structure.mdand scaffold it (usescripts/scaffold-selenium-bdd.mjs) - Write feature files — craft expressive Gherkin scenarios following the guidelines in
references/feature-files.md - Implement Page Objects or Screenplay — use
references/page-object-model.mdfor POM orreferences/screenplay-pattern.mdfor Screenplay - Wire up step definitions and hooks — see
references/step-definitions.mdandreferences/hooks-and-context.mdfor dependency injection patterns - Configure reporting and CI/CD — set up ExtentReports + Cucumber native reporters (
references/reporting.md), parallel execution (references/parallel-execution.md), and GitHub Actions / Docker Grid (references/ci-cd.md)
What ships with it
20 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/features/sample.feature 2.0 KB
- assets/pages/LoginPage.java 3.1 KB
- assets/pom-base/pom.xml 6.0 KB
- assets/runners/TestRunner.java 1.3 KB
- assets/steps/SampleSteps.java 4.9 KB
- assets/support/DriverManager.java 4.7 KB
- assets/support/Hooks.java 4.0 KB
- evals/evals.json 8.5 KB
- references/anti-patterns.md 6.6 KB
- references/ci-cd.md 7.1 KB
- references/feature-files.md 5.4 KB
- references/hooks-and-context.md 7.3 KB
- references/maven-setup.md 5.7 KB
- references/page-object-model.md 7.2 KB
- references/parallel-execution.md 5.8 KB
- references/project-structure.md 7.3 KB
- references/reporting.md 6.2 KB
- references/screenplay-pattern.md 7.6 KB
- references/step-definitions.md 6.1 KB
- scripts/scaffold-selenium-bdd.mjs 24 KB runs code
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.
- 2mo ago First seen · 113 lines · 201 tokens per session scan A 59356337882c
selenium-cucumber-expert is a skill published in the GitHub repository jmr85/e2e-agent-skills (14 stars, last pushed 4mo ago), licensed MIT. It adds 201 tokens to every session and 1,630 once invoked, about $0.0008 per session on Opus 5.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 skills, from other repositories
playwright
Browser automation, web testing, dynamic scraping, and visual verification using Playwright and agent-browser CLI. Supports DOM snapshots with @eN element references, form interactions, and screenshot validations.
browser-test-loop
Use to actually verify a web change in a real browser instead of assuming it works — click through a flow, catch console errors, check a form submits, confirm a fix on the page. Trigger when a UI change needs proof, a bug only reproduces in the browser, or the user asks to test, check, or screenshot the running app.
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
qa
Exercise the delivered customer journey using real runtime or browser evidence. Use for functional acceptance testing after implementation, including failure paths.
playwright
Playwright end-to-end testing best practices for web applications, covering test design, locator strategies, and assertion patterns.
playwright-cursor-rules
Expert guidance for Playwright end-to-end testing with TypeScript and JavaScript best practices.