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 GktuOktay/ai-skills --skill e2e-testergit clone --depth 1 https://github.com/GktuOktay/ai-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/gktuoktay/ai-skills/e2e-tester)<a href="https://agentmods.dev/skills/gktuoktay/ai-skills/e2e-tester"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/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/gktuoktay/ai-skills/e2e-tester"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/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.00066 | $0.01106 |
| Opus 5.5 | $0.00026 | $0.00442 |
| Sonnet 5.5 | $0.00013 | $0.00221 |
| Haiku 4.5 | $0.00007 | $0.00111 |
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 1mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Tester Guidelines
As an E2E (End-to-End) Tester, you validate complete user journeys across the entire application stack. You simulate real user interactions using tools like Playwright, Cypress, or Appium to ensure that all integrated components function seamlessly together.
Core Philosophy
- User-Centric: Test flows exactly as a user would experience them.
- Resilience: Tests should be robust against minor UI changes and network delays.
- Scope: Focus on critical business flows; do not duplicate exhaustive unit tests.
- Environment: Run tests in an environment that closely mirrors production.
DOM Querying Strategies
Selecting elements reliably is crucial for preventing flaky tests.
| Strategy | Priority | Description | Example |
|---|---|---|---|
| Accessibility Roles | Highest | Queries based on accessibility attributes (ARIA). | getByRole('button', { name: 'Submit' }) |
| Data Attributes | High | Using dedicated attributes like data-testid. |
getByTestId('submit-btn') |
| Text Content | Medium | Querying by visible text on the page. | getByText('Welcome back!') |
| CSS Selectors | Low | Querying by classes or IDs (prone to breaking). | .btn-primary or #submit |
| XPath | Lowest | Fragile structure-based queries. Avoid if possible. | //div[1]/span/button |
Best Practice: Advocate for data-testid attributes or proper ARIA roles in the application code.
User Journey Definitions
Structure your tests around complete, valuable user journeys.
// Playwright Example: User Checkout Journey
import { test, expect } from '@playwright/test';
test.describe('E-Commerce Checkout Journey', () => {
test('User can successfully add item to cart and checkout', async ({ page }) => {
// 1. Navigate and Search
await page.goto('https://shop.example.com');
await page.getByPlaceholder('Search products').fill('Wireless Headphones');
await page.keyboard.press('Enter');
// 2. Select and Add to Cart
await page.getByRole('link', { name: 'Noise Cancelling Headphones X1' }).click();
await page.getByRole('button', { name: 'Add to Cart' }).click();
await expect(page.getByText('1 item in cart')).toBeVisible();
// 3. Checkout
await page.getByRole('button', { name: 'Proceed to Checkout' }).click();
// ... Fill forms using semantic queries ...
// 4. Verify Success
await expect(page.getByRole('heading', { name: 'Order Confirmed' })).toBeVisible();
});
});
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.
- 1mo ago First seen · 109 lines · 66 tokens per session scan A f944e616da36
e2e-tester is a skill published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 1,106 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-08-31.
Other skills, from other repositories
external-site-profile-learning
Use this skill when investigating, adding, validating, or debugging external website profiles for the 99idea Playwright browser demo. It teaches how to probe selectors, classify failure modes, add config-driven profiles, and validate both heuristic and Gemini flows.
appium-skill
Generates production-grade Appium mobile automation scripts for Android and iOS in Java, Python, or JavaScript. Supports real device and emulator testing locally and on TestMu AI cloud with 100+ real devices.
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
quinn
Verifies specified behavior through appropriate tests and truthful coverage reports.
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…