Borrowing it
Nothing to install: this file belongs to pwrdrvr/PwrSnap. 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/pwrdrvr/PwrSnap/main/.agents/skills/e2e-docker-repro/SKILL.mdgit clone --depth 1 https://github.com/pwrdrvr/PwrSnapWrote 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/pwrdrvr/pwrsnap/e2e-docker-repro)<a href="https://agentmods.dev/skills/pwrdrvr/pwrsnap/e2e-docker-repro"><img src="https://agentmods.dev/badge/skills/pwrdrvr/pwrsnap/e2e-docker-repro/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/pwrdrvr/pwrsnap/e2e-docker-repro"><img src="https://agentmods.dev/badge/skills/pwrdrvr/pwrsnap/e2e-docker-repro.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.00084 | $0.01122 |
| Opus 5 | $0.00042 | $0.00561 |
| Sonnet 5 | $0.00017 | $0.00224 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
e2e-docker-repro 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Docker Repro
Use this skill to reproduce PwrSnap Desktop E2E failures locally in the Linux Docker harness under scripts/e2e.
Start Here
-
Read the reported CI failure first: failing job URL, test name, timeout, stack trace, and whether Playwright marked it
flaky. -
Check the local branch and diff before running anything:
git status --short --branch git log --oneline -3 --decorate -
Prefer a focused repro before a full-suite run. Use the exact Playwright title substring from CI when possible.
-
Start on Docker's native Linux platform. Use
--platform linux/amd64only when the failure looks architecture-specific or you need exact GHA x86 parity; it is much slower on Apple Silicon.
Commands
Run from the repository root.
Focused stress run against the current worktree:
PWRSNAP_E2E_STAGE=/tmp/pwrsnap-e2e-stage \
./scripts/e2e/run-docker.sh \
--test '<Playwright title or grep pattern>' \
--iterations 30 \
--keep-stage
Full GHA-style Desktop E2E job:
PWRSNAP_E2E_STAGE=/tmp/pwrsnap-e2e-stage \
./scripts/e2e/run-docker.sh --keep-stage
Equivalent root pnpm entrypoint:
pnpm test:desktop-e2e:docker --keep-stage
Run a different ref without switching the worktree:
git fetch origin
PWRSNAP_E2E_STAGE=/tmp/pwrsnap-e2e-stage \
./scripts/e2e/run-docker.sh \
--ref origin/<branch-or-ref> \
--test '<pattern>' \
--iterations 30 \
--keep-stage
Drop into the staged container for ad-hoc inspection:
PWRSNAP_E2E_STAGE=/tmp/pwrsnap-e2e-stage \
./scripts/e2e/run-docker.sh --shell
Workflow
- Reproduce the failure with a focused
--testpattern and--iterations. The wrapper runs Playwright with--retries 0in iteration mode, so every failure is a real first-attempt failure. - If the failure only appears in CI mode, run the full suite. Full-suite mode
executes the root
pnpm run test:desktop-e2eunderxvfb-run, matching GHA. - Preserve evidence while investigating:
- Use
--keep-stageso/tmp/pwrsnap-e2e-stageremains inspectable. - Read
apps/desktop/test-results/.../error-context.mdand traces from the staged tree when Playwright emits them. - Capture the pass/fail rate and exact command in the final report.
- Use
- Instrument narrowly when needed, then remove temporary logging before the final fix. Prefer fixture/test-level logging first for Electron lifecycle failures, then app-level logging only after the failing boundary is known.
- Verify fixes with both a focused stress run and a full-suite run when the original failure came from CI.
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 · 119 lines · 84 tokens per session scan A 8b43614a3599
e2e-docker-repro is a skill published in the GitHub repository pwrdrvr/PwrSnap (5 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 1,122 once invoked, about $0.0004 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
k8s-sidecar-testing
Test the nat464-sidecar demo topology in a selected Kubernetes test namespace, verify IPv6 translation paths, and compare HTTP latency. Includes optional disposable Multipass/k3s setup.
qa-testing
Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…
verify
Build the computer-use-demo image and drive the Streamlit UI headlessly to verify changes end-to-end.
zero-script-qa
Zero Script QA — test without scripts using structured JSON logging and Docker monitoring. Triggers: zero-script-qa, log testing, docker logs, QA.
local-test
Build, run, and test IronClaw locally using Docker containers and Chrome MCP browser automation.
screenshot-automation
Generates an automated App Store screenshot pipeline with UI tests for screenshot capture, device framing, localized caption overlays, and multi-size batch export. Use when user wants automated screenshots, App Store screenshot generation, or a fastlane snapshot replacement.