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 yonatangross/orchestkit --skill testing-e2egit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/testing-e2e)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/testing-e2e"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/testing-e2e/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/yonatangross/orchestkit/testing-e2e"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/testing-e2e.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 145 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 155 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00055 | $0.02966 |
| Opus 5.5 | $0.00022 | $0.01186 |
| Sonnet 5.5 | $0.00011 | $0.00593 |
| Haiku 4.5 | $0.00006 | $0.00297 |
Grade A, and why
testing-e2e 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 20d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Testing Patterns
End-to-end testing with Playwright 1.59+, visual regression, accessibility, and AI agent workflows.
Quick Reference
| Category | Rules | Impact | When to Use |
|---|---|---|---|
| emulate Backends | rules/emulate-e2e.md |
HIGH | FIRST CHOICE — deterministic API backends for E2E |
| Playwright Core | rules/e2e-playwright.md |
HIGH | Semantic locators, auto-wait, flaky detection |
| Page Objects | rules/e2e-page-objects.md |
HIGH | Encapsulate page interactions, visual regression |
| AI Agents | rules/e2e-ai-agents.md |
HIGH | Planner/Generator/Healer, init-agents |
| A11y Playwright | rules/a11y-playwright.md |
MEDIUM | Full-page axe-core scanning with WCAG 2.2 AA |
| A11y CI/CD | rules/a11y-testing.md |
MEDIUM | CI gates, jest-axe unit tests, PR blocking |
| End-to-End Types | rules/validation-end-to-end.md |
HIGH | tRPC, Prisma, Pydantic type safety |
Total: 7 rules, 2 references, 3 checklists, 1 example, 1 script
Upstream coverage (do not restate)
Playwright, axe-core and jest-axe document themselves. This skill carries only the
OrchestKit delta (references/ork-delta.md) plus the house subsets in rules/. Fetch
the vendor page for anything below instead of expecting it here.
| Topic | Source |
|---|---|
Screenshot comparison workflow, baseline files, snapshotPathTemplate |
https://playwright.dev/docs/test-snapshots |
toHaveScreenshot options: mask, maxDiffPixelRatio, stylePath, animations |
https://playwright.dev/docs/api/class-pageassertions |
Auth reuse: storageState, setup projects, IndexedDB |
https://playwright.dev/docs/auth |
Network interception with page.route (the house default is still emulate first, see rules/emulate-e2e.md) |
https://playwright.dev/docs/mock |
| Removed and changed APIs per release (SKILL.md keeps only the short denylist below) | https://playwright.dev/docs/release-notes |
Full locator API surface (the house priority ladder stays in rules/e2e-playwright.md) |
https://playwright.dev/docs/locators |
Playwright runner setup on CI (the house a11y gate workflow stays in rules/a11y-testing.md) |
https://playwright.dev/docs/ci |
init-agents CLI flags and generated files (the Planner/Generator/Healer workflow stays in rules/e2e-ai-agents.md) |
https://playwright.dev/docs/test-agents |
jest-axe matcher and configureAxe API (the house component-state subset stays in rules/a11y-testing.md) |
https://github.com/NickColley/jest-axe |
| Lighthouse CI configuration and score assertions | https://github.com/GoogleChrome/lighthouse-ci |
What ships with it
16 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.
- checklists/a11y-testing-checklist.md 8.5 KB
- checklists/e2e-checklist.md 3.0 KB
- checklists/e2e-testing-checklist.md 12 KB
- examples/orchestkit-e2e-tests.md 21 KB
- references/ork-delta.md 2.9 KB
- references/playwright-setup.md 3.6 KB
- rules/_sections.md 1.2 KB
- rules/a11y-playwright.md 1.9 KB
- rules/a11y-testing.md 3.6 KB
- rules/e2e-ai-agents.md 2.2 KB
- rules/e2e-page-objects.md 2.2 KB
- rules/e2e-playwright.md 2.7 KB
- rules/emulate-e2e.md 3.6 KB
- rules/validation-end-to-end.md 2.8 KB
- scripts/create-page-object.md 1.9 KB
- test-cases.json 3.0 KB
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.
- 20d ago Changed 15952d3cdfb6
- 21d ago Changed · -5 lines 99515aadbb28
- 22d ago Changed · -1 lines bf0314f32d54
- 1mo ago Changed 8eafca80c852
- 1mo ago First seen · 263 lines · 55 tokens per session scan A 9d15764e16bc
testing-e2e is a skill published in the GitHub repository yonatangross/orchestkit (298 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 2,966 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
jira-validate-production
Check that the fix a Jira issue carries is live on the PRODUCTION site and behaves as the issue asked, then close the card, or open a follow-up issue for what failed. Insert into the prompt of a run started on a batch of merged issues, or of a Jira post-deploy column rule.
browser-qa
Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console errors and screenshot evidence. Use on a web surface end to end, or to reproduce a front-end bug.
web-system-tests
The web realization of the system-tests contract — browser-driven system tests with Playwright against a running frontend. Owns the project layout (tests/), the Playwright configuration (baseURL plus webServer, cross-engine projects), the role- and label-based selector policy, code coverage as an opt-in second run…
system-tests
Generic, composable conventions for system tests — black-box tests exercising the running system from the outside through its public surface. Defines the stack-neutral contract (no internals, environment coordinates as configuration, test isolation, total verdict reporting) and the taxonomy of expectation origins…