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/maintain-verification-skill/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/maintain-verification-skill)<a href="https://agentmods.dev/skills/openwong2kim/wmux/maintain-verification-skill"><img src="https://agentmods.dev/badge/skills/openwong2kim/wmux/maintain-verification-skill/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/maintain-verification-skill"><img src="https://agentmods.dev/badge/skills/openwong2kim/wmux/maintain-verification-skill.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.00073 | $0.01340 |
| Opus 5.5 | $0.00029 | $0.00536 |
| Sonnet 5.5 | $0.00015 | $0.00268 |
| Haiku 4.5 | $0.00007 | $0.00134 |
Grade A, and why
maintain-verification-skill 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 15d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain a verification skill
A feature map rots the moment the app changes. This skill is the upkeep loop for a skill generated by /create-verification-skill; in this repo that is .claude/skills/verify-wmux/ with its driver scripts/control-wmux.mjs. The unit of rigor is the feature, not every sentence: cover every feature file from source and exercise every feature live, without turning every bullet into a terminal command.
Outcomes
Pick one, and say which:
- clean: every feature got source and live coverage; nothing worth shipping. No branch, no PR.
- changed: one PR ships proven doc, harness, or map corrections.
- blocked: coverage could not finish or a proven fix could not ship safely. Say exactly what blocked it.
Edit scope
Only edit the verification skill's own files: .claude/skills/verify-wmux/ (SKILL.md, references/features/), the driver scripts/control-wmux.mjs, its pure helpers scripts/lib/control-wmux-lib.mjs and their test scripts/__tests__/controlWmux.test.mjs. Never edit product code during a run: a behavior the map describes that the app no longer does is either doc drift (fix the map) or a product regression (report it, don't paper over it in docs).
Pass
-
Locate the target. Find the verification skill to maintain: the project-local skill whose body has Launch/Doctor/Drive sections and a feature map (
.claude/skills/verify-*/). Several candidates → ask which one; none → stop and point at/create-verification-skillinstead of inventing a target. -
Index hygiene. Read
references/features/README.mdand glob its sibling files. Fix missing, extra, duplicate, or dead entries. Lightweight; no generated inventory.
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.
- 15d ago First seen · 47 lines · 73 tokens per session scan A 4862ae2d5d42
maintain-verification-skill is a skill published in the GitHub repository openwong2kim/wmux (437 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 1,340 once invoked, about $0.0003 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-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…