Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ngocsangyem/MeowKit --skill qa-manualgit clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/qa-manual)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/qa-manual"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/qa-manual/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/ngocsangyem/meowkit/qa-manual"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/qa-manual.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.00091 | $0.01342 |
| Opus 5 | $0.00046 | $0.00671 |
| Sonnet 5 | $0.00018 | $0.00268 |
| Haiku 4.5 | $0.00009 | $0.00134 |
Grade A, and why
mk:qa-manual 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 5d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Manual Testing & E2E Code Generation
Orchestrates browser skills to act like a human tester: navigate, interact, verify, and report.
When to Use
Trigger: "test this flow", "QA this page", "generate E2E tests", "test login flow", "manual testing", "write Playwright tests for"
Explicit:
/mk:qa-manual tasks/plans/260315-auth-flow.md --report→ manual QA report/mk:qa-manual tasks/plans/260315-checkout.md --generate→ Playwright .spec.ts/mk:qa-manual https://app.example.com→ explore and test from URL/mk:qa-manual [spec]→ auto-detect use case from spec content
Workflow Integration
Operates in Phase 4 (Review) for QA reports or Phase 3 (Build) for E2E code generation.
Skill Routing
Each action uses the best browser skill:
| Action | Skill | Why |
|---|---|---|
| DOM interaction (click, fill, type) | mk:playwright-cli |
Generates Playwright code as side-effect |
| Navigation + page load | mk:playwright-cli |
goto + wait, code output |
| Visual verification (screenshot) | mk:agent-browser |
Annotated snapshots |
| Auth flow (login, session, MFA) | mk:agent-browser |
Session persistence, auth import |
| Execute Playwright test | Script: npx playwright test |
Deterministic |
Authentication Protocol
On auth encounter (login page, MFA, 401/403):
- STOP current flow immediately
- Show user:
⚠️ Authentication required at: [current URL] mk:qa-manual needs credentials to continue. Please provide: - Username/email: ___________ - Password: ___________ Type 'skip' to skip this flow or 'abort' to stop testing. - WAIT for user input — do NOT proceed without it
- On credentials → fill form using
mk:playwright-cli, continue flow - On 'skip' → mark flow SKIPPED, move to next
- On 'abort' → end session, output partial report
What ships with it
6 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.
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.
- 5d ago First seen · 129 lines · 91 tokens per session scan A 63a2a701699a
mk:qa-manual is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 1,342 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
ui-test
Runs UI tests described in plain English by driving real Chrome via the Claude-in-Chrome extension. Covers end-to-end flows (clicks, forms, assertions), visual checks (screenshot + optional baseline diff), accessibility (axe-core), performance (Web Vitals + light Lighthouse-style metrics), and an interactive --debug…
audit-ui-e2e
Runs a beginner-mind end-to-end UI audit of any running app — local dev server, staging, production, or a specific URL. Drives Chrome through every interactive element on the target surface, collects structured findings (severity, category, where, symptom, impact, repro, triage), and hands the result off to…
capture-screens
Automatically navigates a web app using Playwright MCP and captures context-aware named screenshots at each product feature state. Names each file semantically based on context (e.g., checkout-payment-form-filled.png). Outputs a manifest.json mapping filenames to descriptions and a summary report. Use when documenting…
verify
How to run and drive this app to verify UI/server changes at runtime.
playwright-ops-demo-playwright-browser
Use when running playwright browser workflows for playwright-ops-demo.
skill-playwright
Browser automation and end-to-end testing with Playwright. Use when building/testing frontends, automating user workflows, taking screenshots, validating UI state, filling forms, testing across browsers, or mentions "playwright", "E2E test", "browser automation", "screenshot".