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 niels-emmer/myace --skill end-to-end-testinggit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/end-to-end-testing)<a href="https://agentmods.dev/skills/niels-emmer/myace/end-to-end-testing"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/end-to-end-testing/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/niels-emmer/myace/end-to-end-testing"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/end-to-end-testing.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.00028 | $0.00280 |
| Opus 5.5 | $0.00011 | $0.00112 |
| Sonnet 5.5 | $0.00006 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
End-to-End Testing 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.
What it actually says
Purpose
Catch integration bugs that layer-isolated tests miss.
When to use it
For every feature that spans frontend and backend.
Checklist
- Scope: test critical user journeys (login, CRUD, error paths) — not every UI permutation.
- Structure: use page objects or fixtures for maintainable test code.
- Environment: dedicated test database, clean state per test run.
- Data seeding: set up test data as part of the test, not in shared fixtures.
- Flakiness prevention: use wait strategies for async operations, retry on transient failures.
- CI integration: run E2E tests in CI, not just locally. Fail the build on E2E failures.
Expected output
A suite of E2E tests covering the critical paths of each feature, running in CI with reliable pass/fail results.
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 · 29 lines · 28 tokens per session scan A 9a1a96201eba
End-to-End Testing is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 280 once invoked, about $0.0001 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-03.
Other skills, from other repositories
loom-e2e-testing
End-to-end testing for web applications with Playwright, Cypress, Selenium, and Puppeteer.
loom-test-strategy
Test strategy guidance covering pyramid design, coverage, test categorization, flaky tests, infrastructure, and risk-based prioritization.
loom-testing
Test implementation across unit, integration, e2e, security, infrastructure, data pipeline, and ML domains.
review-implementation-qa
Implementation review QA axis - live-runs the assembled feature for functional defects.
aif-test
Run unit, integration, e2e and UI tests with coverage analysis, build verification, visual regression and QA reports.
aif-web-testing
Test web apps with Playwright, Vitest and k6: E2E, unit, integration, load, security, visual and a11y.