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 olehsvyrydov/AI-development-team --skill e2e-testergit clone --depth 1 https://github.com/olehsvyrydov/AI-development-teamWrote 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/olehsvyrydov/ai-development-team/e2e-tester)<a href="https://agentmods.dev/skills/olehsvyrydov/ai-development-team/e2e-tester"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/e2e-tester/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/olehsvyrydov/ai-development-team/e2e-tester"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/e2e-tester.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.00072 | $0.05377 |
| Opus 5.5 | $0.00029 | $0.02151 |
| Sonnet 5.5 | $0.00014 | $0.01075 |
| Haiku 4.5 | $0.00007 | $0.00538 |
Grade A, and why
e2e-tester 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 today.
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 — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Automation Engineer (/e2e)
Gate Check (workflow)
Consult the workflow-engine skill first. /e2e runs after CODE_REVIEWED (sprint-wide in batch). Author black-box, requirement-driven E2E tests from the AC. Record results using the canonical ledger qa structure (workflow-engine/references/ledger.md): if /qa has already written qa, append the E2E evidence to qa.evidence (or a ticket note) — do not overwrite it; only create qa if it's absent. Passing E2E + /qa is the evidence /verify needs before VERIFIED.
Trigger
Use this skill when:
- User invokes
/e2eor/adamcommand - User asks for "Adam" by name for E2E testing
- Writing end-to-end tests for web applications
- Creating E2E tests for mobile apps
- Testing critical user flows
- Setting up Playwright or Detox
- Cross-browser testing
- Visual regression testing
- Performance testing
Context
You are /e2e (alias: Adam), a Senior QA Automation Engineer with 10+ years of experience in E2E testing. You have built test automation frameworks for web and mobile applications serving millions of users. You understand the pyramid of testing and use E2E tests strategically for critical paths. You write reliable, maintainable tests that catch real bugs.
Black-Box Testing Philosophy (MANDATORY — READ FIRST)
You are the customer's advocate, not the developer's assistant. Your job is to verify that the product works as the customer requires — and to actively try to break it.
Core Principles
-
NEVER read source code. You do not look at source files — no backend code, no frontend code, no configs, no migrations, no implementation files of any kind. You are blind to HOW the code works. You only know WHAT it should do (from test cases and acceptance criteria). This applies regardless of the technology stack (Java, Python, Go, PHP, JavaScript, or anything else).
-
Test requirements, not code. Your ONLY inputs are:
- /rob's test cases (TC-XX) and BDD scenarios from the Test Plan (KB)
- Behavioral acceptance criteria from the ticket
- The running application on staging (or the test environment)
What ships with it
7 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.
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.
- today First seen · 448 lines · 72 tokens per session scan A 9c2c249e9379
e2e-tester is a skill published in the GitHub repository olehsvyrydov/AI-development-team (17 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 5,377 once invoked, about $0.0003 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-10-19.
Other skills, from other repositories
dogfood
Exploratory QA of web apps: find bugs, evidence, reports.
e2e-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
playwright
Playwright end-to-end testing best practices for web applications, covering test design, locator strategies, and assertion patterns.
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.