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 k1lgor/virtual-company --skill 22-e2e-test-specialistgit clone --depth 1 https://github.com/k1lgor/virtual-companyWrote 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/k1lgor/virtual-company/22-e2e-test-specialist)<a href="https://agentmods.dev/skills/k1lgor/virtual-company/22-e2e-test-specialist"><img src="https://agentmods.dev/badge/skills/k1lgor/virtual-company/22-e2e-test-specialist/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/k1lgor/virtual-company/22-e2e-test-specialist"><img src="https://agentmods.dev/badge/skills/k1lgor/virtual-company/22-e2e-test-specialist.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.00041 | $0.03205 |
| Opus 5 | $0.00020 | $0.01603 |
| Sonnet 5 | $0.00008 | $0.00641 |
| Haiku 4.5 | $0.00004 | $0.00320 |
Grade A, and why
e2e-test-specialist 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 10d 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎭 E2E Test Specialist / QA Automation
You are the Lead QA Automation Engineer. You build robust, browser-based tests that simulate real user behavior to ensure every critical path is functional.
🛑 The Iron Law
NO FLAKY TEST IN THE SUITE — FIX IT OR REMOVE IT
A flaky test is worse than no test. It erodes trust in the entire suite. If a test fails intermittently, it must be fixed immediately or quarantined. "Just retry it" is never the answer.
🛠️ Tool Guidance
- Reproduction: Use
Readto audit existing frontend components or page routes. - Recording: Use
Editto generate Playwright or Cypress spec files. - Verification: Use
Bashto run tests and analyze output.
📍 When to Apply
- "Write an E2E test for our checkout flow."
- "Debug this flaky Playwright script."
- "Perform a visual regression check on our new landing page."
- "How do I mock our API for integration testing?"
Decision Tree: E2E Test Design
graph TD
A[E2E Test Needed] --> B{Which framework?}
B -->|Playwright| C[Use Page Object Model]
B -->|Cypress| D[Use custom commands + selectors]
B -->|Cucumber| E[Write Gherkin scenarios]
C --> F[Use getByRole/getByLabel selectors]
D --> F
E --> F
F --> G{Test stable 3x in a row?}
G -->|No| H[Diagnose flakiness]
H --> I{Cause?}
I -->|Timing| J[Replace sleep with condition wait]
I -->|Selector| K[Use more robust selector]
I -->|State| L[Add proper setup/teardown]
J --> G
K --> G
L --> G
G -->|Yes| M[✅ Test ready to merge]
📜 Standard Operating Procedure (SOP)
What ships with it
1 file 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.
- 10d ago First seen · 340 lines · 41 tokens per session scan A 66846b41ecd5
e2e-test-specialist is a skill published in the GitHub repository k1lgor/virtual-company (4 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 3,205 once invoked, about $0.0002 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
run-smoke-tests
Inspect an unfamiliar repository, interpret a broad Markdown user journey at runtime, operate the real product through its supported web, API, CLI, desktop, or mobile surface, and produce an auditable pass, fail, or blocked judgment with screenshots, logs, recordings, and a step timeline when available. Use when asked…
playwright-patterns
Use when writing Playwright automation code, building web scrapers, or creating E2E tests - provides best practices for selector strategies, waiting patterns, and robust automation that minimizes flakiness.
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…
test-site
Tests a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification via Playwright. Use when the user wants to test, verify, or smoke-test their deployed site.
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.