Borrowing it
Nothing to install: this file belongs to openwong2kim/wmux. 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/openwong2kim/wmux/main/.claude/skills/verify-wmux/SKILL.mdgit clone --depth 1 https://github.com/openwong2kim/wmuxWrote 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/openwong2kim/wmux/verify-wmux)<a href="https://agentmods.dev/skills/openwong2kim/wmux/verify-wmux"><img src="https://agentmods.dev/badge/skills/openwong2kim/wmux/verify-wmux/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/openwong2kim/wmux/verify-wmux"><img src="https://agentmods.dev/badge/skills/openwong2kim/wmux/verify-wmux.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.00108 | $0.04449 |
| Opus 5.5 | $0.00043 | $0.01780 |
| Sonnet 5.5 | $0.00022 | $0.00890 |
| Haiku 4.5 | $0.00011 | $0.00445 |
Grade B, and why
verify-wmux scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Isolation covers wmux's own paths only. Things outside them are shared with the owner: `~/.claude/settings.json`, `~/.claude.json`, `~/.wmux/hooks/` (Claude Code integration), the `~/.local/bin/wmux` CLI shim, Keychain How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
verify-wmux
Status: proven on macOS against the installed /Applications/wmux.app 4.3.0: launch, doctor, drive (Settings first, then one sweep over all ten feature files), ARIA snapshots and CDP screenshots, stop --purge, evidence kept. Not yet run on Windows or Linux, nor against a dev build; the PC switcher was proven only in its absent state.
wmux is an Electron terminal multiplexer. The surface a user touches is the main window (sidebar, panes with xterm terminals, rail pages, settings, dialogs). Secondary surfaces (the wmux CLI, the MCP server, the phone web client) are not driven by this skill; prove those with a terminal transcript or the repo's own harnesses (e2e/, rig/).
Everything runs through one driver, scripts/control-wmux.mjs (Node 22+, uses the repo's playwright-core dependency; run npm ci once in a fresh checkout). Every command prints one JSON object and exits non-zero on failure. Read references/features/README.md before driving, then the feature file that matches the request.
Launch
node scripts/control-wmux.mjs launch # /Applications/wmux.app, suffix -verify-<random>
node scripts/control-wmux.mjs launch --app <path/to/wmux> # any other packaged build's executable
node scripts/control-wmux.mjs launch --suffix -verify-mytest --timeout 90000
node scripts/control-wmux.mjs launch --app <exe> --env-file vars.json # extra env, applied after the scrub below
node scripts/control-wmux.mjs launch --app <exe> --user-data-dir <dir> # Electron userData at <dir><suffix>
node scripts/control-wmux.mjs launch --app <exe> --fake-audio clip.wav # a WAV plays once as the microphone
What ships with it
12 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.
- .gitignore 87 B
- references/features/browser-panel.md 3.3 KB
- references/features/file-tree.md 3.3 KB
- references/features/first-run-wizard.md 4.6 KB
- references/features/panes-splits.md 3.8 KB
- references/features/pc-switcher.md 2.1 KB
- references/features/rail-pages.md 5.6 KB
- references/features/README.md 6.8 KB
- references/features/rooms.md 6.7 KB
- references/features/settings.md 7.7 KB
- references/features/sidebar-workspaces.md 4.7 KB
- references/features/terminal.md 3.7 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.
- 4d ago Changed · +5 lines b16f7ec2d154
- 5d ago Changed · +6 lines 2070c3a9503e
- 13d ago Changed · +13 lines 9d2cd34847d8
- 15d ago First seen · 141 lines · 108 tokens per session scan B ae874b9393ed
verify-wmux is a skill published in the GitHub repository openwong2kim/wmux (437 stars, last pushed today), licensed MIT. It adds 108 tokens to every session and 4,449 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-13.
Other skills, from other repositories
generate-e2e-tests
Walk a flow in the browser and write end-to-end tests (Playwright, Cypress, etc.) that reproduce it. Use when asked to create e2e coverage for a user flow.
smoke-test
Smoke-test a user flow end to end in a browser (login, checkout, signup, etc.) and verify the expected result. Use when asked to walk through a flow and confirm it still works.
qa-use
E2E testing and browser automation with qa-use CLI. Use when the user needs to run tests, verify features, automate browser interactions, or debug test failures.
alethia
Use Alethia, a patent-pending agent-native software runtime for executing and verifying application workflows, to interact with a real browser, run E2E checks, enforce safety policies, audit accessibility or security, and export signed evidence. Requires the @vitronai/alethia MCP server to be configured. Trigger…
playwright-tabbed-orchestration
Parent Agent uses playwright-tabbed to allocate browser tabs and partition tasks, then spawns child agents in parallel — each operating on its assigned tabid — for browser acceptance testing or automation, with a final aggregated summary. Suitable for multi-page validation, parallel module checks, and…
actionbook-web-test
Run browser-based web tests against websites using Actionbook CLI. Activate when the user wants to test a website workflow, run smoke tests, verify a user flow, check if a web application works, run regression tests, or validate browser-based interactions. Supports test definition, execution, assertion, reporting, and…