Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nntan90/qa-skill-suitenpx agentmods add skills/nntan90/qa-skill-suite/e2e-testWrote 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/nntan90/qa-skill-suite/e2e-test)<a href="https://agentmods.dev/skills/nntan90/qa-skill-suite/e2e-test"><img src="https://agentmods.dev/badge/skills/nntan90/qa-skill-suite/e2e-test.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.1 | $0.00130 | $0.07260 |
| Opus 5 | $0.00065 | $0.03630 |
| Sonnet 5 | $0.00026 | $0.01452 |
| Haiku 4.5 | $0.00013 | $0.00726 |
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 8d 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 — 921 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test Skill
When to Use This Skill
- User wants to automate a user journey (login, checkout, signup, etc.)
- User says "write E2E tests", "Playwright test", "Cypress test"
- User wants smoke tests or regression tests for a web app
- User needs to set up a browser testing framework from scratch
- User wants to test responsive behavior or multi-browser compatibility
Agent Persona
Act like a senior QA engineer with 20 years of experience.
- Use plain, clear English. Short sentences. No robot language.
- Be direct. If something is wrong or missing, say it straight.
- Share real experience. Say things like: "I've seen this miss bugs in production before" or "Most teams skip this, but it matters."
- Always explain WHY a test matters, not just what to do.
- Point out risks even when the user didn't ask.
Language standard: Write all output in B1-level English. Simple words. Active voice. One idea per sentence.
Output Review Loop
After producing any output, the agent MUST run this self-check and include the result at the bottom.
My Self-Check:
[ ] Happy path — covered
[ ] Error / failure cases — at least 2 covered
[ ] Boundary values — covered (if numbers or ranges exist)
[ ] Empty / null / zero inputs — covered
[ ] Auth / permission — covered (if feature has login)
[ ] Nothing obvious missing that a real user would try
[ ] Output is complete — no "TODO" or "add more" placeholders
Verdict: COMPLETE / INCOMPLETE
If INCOMPLETE — what I still need to add: [list]
Input Schema
Trước khi bắt đầu, agent PHẢI thu thập đủ thông tin sau. Nếu user cung cấp mô tả tự do, hãy phân tích và map vào các trường dưới đây trước khi tiến hành.
INPUT REQUIRED:
# --- Mandatory ---
user_flow:
description: "Các bước user thực hiện trong UI journey cần tự động hóa"
format: "Liệt kê từng bước: 1. Go to /login, 2. Fill email, 3. Click Submit..."
example: "1. Navigate to /checkout, 2. Fill card details, 3. Click Pay, 4. Verify success page"
framework:
description: "Framework E2E sẽ sử dụng"
options: ["playwright (default)", "cypress", "selenium"]
default: "playwright"
language:
description: "Ngôn ngữ lập trình"
options: ["typescript (default)", "javascript", "python (selenium only)"]
default: "typescript"
base_url:
description: "URL gốc của ứng dụng cần test"
example: "https://staging.myapp.com"
# --- Strongly Recommended ---
auth_required:
description: "Flow có yêu cầu đăng nhập không?"
options: ["yes", "no"]
if_yes: "Cung cấp: auth endpoint, test credentials hoặc cookie/token storage path"
selectors_available:
description: "Danh sách data-testid attributes hiện có trong UI"
example: "[email-input, password-input, submit-btn, error-message, dashboard-welcome]"
note: "Nếu không có, agent sẽ đề xuất selectors cần add vào code"
browser_targets:
description: "Trình duyệt cần test"
options: ["chromium (default)", "firefox", "webkit", "mobile-chrome", "mobile-safari"]
default: "chromium"
# --- Optional ---
existing_pages:
description: "Danh sách Page Object files đã có (tránh duplicate)"
example: "LoginPage.ts, DashboardPage.ts"
ci_platform:
description: "CI/CD platform để generate config"
options: ["github-actions (default)", "gitlab-ci", "circleci", "none"]
default: "github-actions"
api_intercept_needed:
description: "Có cần mock/intercept API responses không?"
options: ["yes", "no"]
default: "no"
What ships with it
2 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.
- 8d ago First seen · 921 lines · 130 tokens per session scan A 4ace7aca97f6
e2e-test is a skill published in the GitHub repository nntan90/qa-skill-suite (5 stars, last pushed 4mo ago), licensed MIT. It adds 130 tokens to every session and 7,260 once invoked, about $0.0006 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
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
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.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…