Borrowing it
Nothing to install: this file belongs to bitovi/convey. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bitovi/convey/main/.github/skills/debug-e2e-test/SKILL.mdgit clone --depth 1 https://github.com/bitovi/conveyWrote 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/bitovi/convey/debug-e2e-test)<a href="https://agentmods.dev/skills/bitovi/convey/debug-e2e-test"><img src="https://agentmods.dev/badge/skills/bitovi/convey/debug-e2e-test/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/bitovi/convey/debug-e2e-test"><img src="https://agentmods.dev/badge/skills/bitovi/convey/debug-e2e-test.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 36 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 119 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.00056 | $0.01132 |
| Opus 5.5 | $0.00022 | $0.00453 |
| Sonnet 5.5 | $0.00011 | $0.00226 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
debug-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 2mo 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Debug E2E Test
This skill provides a systematic workflow for debugging and fixing failing Playwright E2E tests in the test-app.
When to Use This Skill
Use this skill when:
- A Playwright E2E test is failing
- Asked to fix a failing test
- Investigating why tests are broken
- Tests pass locally but fail in CI
- Need to understand what a test failure means
Prerequisites
- Dev server must be running (
cd test-app && npm run dev) - Playwright MCP tools available
- Failed test has generated artifacts in
test-results/
Screenshot Output
Playwright MCP is configured to save screenshots to the workspace-level temp/ directory (set via --output-dir in .vscode/mcp.json). Screenshots taken during live debugging with MCP tools will appear there. The temp/ folder is gitignored.
Debugging Workflow
Step 1: Run the Specific Failed Test
Run ONLY the specific failing test using the -g flag to get focused output:
npx playwright test <test-file>.spec.ts -g "test name"
Step 2: Analyze the Test Output
Read the terminal output carefully and extract:
- Test location: File path and line number
- Failure type: What assertion failed
- Expected vs Actual: What the test expected vs what it got
- Error message: The specific error
- Artifact paths: Screenshot and error-context locations
Step 3: Load the Screenshot
Test-run failure screenshots land in:
test-results/<test-name>/test-failed-1.png
Screenshots taken manually during MCP exploration land in:
temp/
Use the read_media_file tool (or the Playwright MCP screenshot tool) to view either.
Step 4: Read the Error Context
Read the error-context.md file from the test results directory.
Key things to look for:
- Are the elements the test is looking for present?
- Are there unexpected elements?
- Are there console errors indicating broken functionality?
- Is the page structure what the test expects?
Step 5: Read the Test Code
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.
- 2mo ago First seen · 135 lines · 56 tokens per session scan A f25f495e78cd
debug-e2e-test is a skill published in the GitHub repository bitovi/convey (47 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 1,132 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-08-30.
Other skills, from other repositories
test-fix
Automatically invoke when any test run produces failures: FAIL output, test errors, or assertion failures in unit or E2E suites. Do NOT wait for the user to ask. Hard limit of 3 fix attempts per failure, then stops and escalates. Trigger on: "tests are failing", "fix the tests", "tests are broken".
cgs-test-flakiness
Use for test flakiness tasks that diagnose flaky tests by isolating timing, randomness, ordering, environment, and cleanup causes; produce verification evidence, changed or proposed files, and handoff boundaries.
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
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.…
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
evidence-audit
Evidence-led audit/fix rounds for any codebase in any language. Finds only defects that a runnable proof reproduces on current code, applies the narrowest in-scope patch, verifies with a second proof, promotes high-risk proofs to permanent regression tests, and reports exact validation results. Use whenever the user…