OpenCode is an open-source AI coding agent that helps developers work on software projects. It includes agents for full-access development, read-only exploration and planning, plus a general subagent for complex searches and multistep tasks; the catalogue add-ons extend its workflows.
Borrowing it
Nothing to install: this file belongs to anomalyco/opencode. 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/anomalyco/opencode/dev/.opencode/skills/app-e2e-tests/SKILL.mdgit clone --depth 1 https://github.com/anomalyco/opencodeWrote 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/anomalyco/opencode/app-e2e-tests)<a href="https://agentmods.dev/skills/anomalyco/opencode/app-e2e-tests"><img src="https://agentmods.dev/badge/skills/anomalyco/opencode/app-e2e-tests/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/anomalyco/opencode/app-e2e-tests"><img src="https://agentmods.dev/badge/skills/anomalyco/opencode/app-e2e-tests.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.00119 | $0.04979 |
| Opus 5.5 | $0.00048 | $0.01992 |
| Sonnet 5.5 | $0.00024 | $0.00996 |
| Haiku 4.5 | $0.00012 | $0.00498 |
Grade A, and why
app-e2e-tests 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 7d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App e2e tests
Read packages/app/e2e/AGENTS.md and the Tests section of packages/app/AGENTS.md first. They define what to test, which locators to use, and how to assert. packages/app/README.md (E2E Testing) documents run modes and env vars. This skill covers what makes these tests slow or flaky in CI, which runs the suite as two shards per OS on 4-vCPU runners (.github/workflows/test.yml:207-229). Most races below were found on Windows.
All paths below are relative to packages/app unless they start with packages/, services/ or .github/.
What a test runs against
- No opencode backend. Each shard leg runs
bun --cwd packages/app test:e2e:built --shard=<n>/2(test.yml:274-279). It builds once and starts one Bun static server,e2e/utils/serve.ts, on127.0.0.1:${PLAYWRIGHT_PORT ?? 3000}. All 5 workers share it (playwright.config.ts:23-27).serve.tskeeps vite preview's SPA fallback rules. Do not move built e2e back to vite preview. On case-insensitive file systems it synchronously reads the wholedist/_assetsdirectory (about 3,100 files) for every asset request, so every worker's page loads wait in line. Thee2e/performanceconfigs still use it to keep their baselines comparable.
- The API is an in-memory mock per page, running in the test worker.
mockOpenCodeServer(e2e/utils/mock-server.ts:202):- answers
page.route("**/api/**")with an Effect HttpApi handler; - fakes
/api/eventSSE with an init-scriptfetchoverride; - serves PTY sockets through
routeWebSocket.
- answers
- Unmocked routes fail the test with a 501 and
Unmocked API request(mock-server.ts:403-411). Add the route tomock-server.tsonce instead of routing around it in a spec. - Build pages with the helpers:
mockWorkspace,openSession,openDraft,openWorktreeDraft,mockRemoteServer,openSettings(e2e/utils/workspace.ts);setupTimeline(e2e/utils/timeline.ts:209) for streamed timelines,mockServers(mock-server.ts:495) for several origins;seed(e2e/utils/app.ts:61) for storage,holdRoute(app.ts:207) to hold requests until you release them.
- Deliver events with the mock's
push, which buffers until the app connects, or withinstallSseTransport(e2e/utils/sse-transport.ts:60), whosesendresolves on delivery. Afterpage.reload(), awaittransport.waitForConnection()before sending (e2e/regression/timeline-stream.spec.ts:1700-1702). - Windows-only failures are races, not Windows code paths. Mock directories are
C:/OpenCode/<name>on every OS (workspace.ts:33), and nothing touches the disk. Lazy chunks, stylesheets and responses finish out of order more often on the Windows runners.
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.
- 7d ago First seen · 139 lines · 119 tokens per session scan A de3b6c0d48e3
app-e2e-tests is a skill published in the GitHub repository anomalyco/opencode (220,205 stars, last pushed today), licensed MIT. It adds 119 tokens to every session and 4,979 once invoked, about $0.0005 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-10-16.
Other skills, from other repositories
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
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.…
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…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
critique
Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.