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 skills/dongduong2001/pudo-code-system/e2enpx skills add DongDuong2001/pudo-code-system --skill e2egit clone --depth 1 https://github.com/DongDuong2001/pudo-code-systemWrote 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/dongduong2001/pudo-code-system/e2e)<a href="https://agentmods.dev/skills/dongduong2001/pudo-code-system/e2e"><img src="https://agentmods.dev/badge/skills/dongduong2001/pudo-code-system/e2e.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 | $0.00014 | $0.00187 |
| Opus 5 | $0.00007 | $0.00093 |
| Sonnet 5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
e2e-test 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 5d 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
End-to-End (E2E) Test Skill
This skill handles full-stack browser and user-journey automation testing.
When to use this skill
- When verifying critical business flows (e.g., User Signup, Checkout, Payment).
- When using tools like Playwright, Cypress, or Selenium.
- When testing the actual deployed frontend against a real environment.
Guidelines
- High ROI Flows: Only E2E test the most critical user journeys. These tests are slow and brittle.
- Resilient Selectors: Prefer querying elements by testing-specific data attributes (e.g.,
data-testid) or ARIA roles rather than fragile CSS classes. - Avoid Sleep: Never use hardcoded wait/sleep times. Wait for specific network requests to complete or elements to become visible/interactive.
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.
- 5d ago First seen · 19 lines · 14 tokens per session scan A 1d49d794cdbd
e2e-test is a skill published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 28d ago), licensed MIT. It adds 14 tokens to every session and 187 once invoked, about $0.0001 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-31.
Other skills, from other repositories
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…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
selenium-cucumber-expert
Use when writing E2E tests with Selenium WebDriver and Cucumber BDD in Java, setting up BDD test infrastructure with Maven or Gradle, writing Gherkin feature files, implementing step definitions in Java, configuring Page Object Model or Screenplay Pattern, setting up parallel execution, generating ExtentReports or…
playwright-automation-expert
Use when writing E2E tests with Playwright, setting up test infrastructure, debugging flaky browser tests, organizing project structure, or testing REST APIs. Invoke for browser automation, E2E tests, Page Object Model, test flakiness, visual testing, project scaffolding, folder layout, API testing, JSON schema…
cm-browse
Use when you need visual QA, screenshots, or post-deploy smoke testing through a real browser with Playwright.
playwright-skill
Battle-tested Playwright patterns for writing, debugging, and scaling reliable test suites. Use when you need guidance for E2E, API, component, visual, accessibility, or security testing, plus CI/CD, CLI automation, page objects, and migration from Cypress or Selenium. TypeScript and JavaScript.