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 testinggit 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/testing)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/testing"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/testing/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/testing"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/testing.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.00067 | $0.00662 |
| Opus 5.5 | $0.00027 | $0.00265 |
| Sonnet 5.5 | $0.00013 | $0.00132 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
mk:testing 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 1mo 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Toolkit
Reference guides for testing: TDD red-green-refactor, validation scripts, and visual QA.
When to Use
- During Phase 2 (Test) for writing tests — failing tests first in TDD mode (
--tdd/MEOWKIT_TDD=1), or any-order tests in default mode - During Phase 3 (Build) for verifying implementation
- When the
testeragent needs testing patterns - For visual QA testing of web applications
Workflow Integration
Operates in Phase 2 (Test) and Phase 3 (Build). Output supports the tester agent.
In TDD mode the cycle is RED → GREEN → REFACTOR (failing tests required before implementation). In default mode (TDD off), tests may be written before, alongside, or after implementation — the developer chooses.
References
| Reference | When to load | Content |
|---|---|---|
| red-green-refactor.md | Phase 2-3 | TDD cycle, test-first rules, refactoring guidelines |
| validation-scripts.md | After code changes | Running validation scripts, interpreting results |
| visual-qa.md | UI testing | Browser-based visual QA, screenshot comparison, responsive testing |
| e2e-best-practices.md | When creating E2E tests | Tool preference, locator strategy, wait patterns, POM, flaky quarantine, success metrics |
Gotchas
- Mocks hiding integration failures: All mocked tests pass but real service calls fail → Use integration tests for critical paths; mock only external third-party services
- Test coverage metric gamed by trivial assertions: 100% coverage with
expect(true).toBe(true)→ Measure mutation testing score alongside coverage; flag tests with zero assertions - Vue-specific test design/review: for designing or auditing Vitest + Vue Test Utils tests (components, composables, Pinia, router, Suspense, Teleport) → use
mk:vue-testing-best-practices(advisory/review only; this skill still owns running tests + TDD)
What ships with it
4 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.
- 1mo ago First seen · 49 lines · 67 tokens per session scan A 0cb9ccd5969c
mk:testing is a skill published in the GitHub repository ngocsangyem/MeowKit (15 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 662 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-09-03.
Other skills, from other repositories
testing-expert
Expert-level software testing with unit tests, integration tests, E2E tests, TDD/BDD, and testing best practices. Use when the user mentions TDD, BDD, unit tests, integration tests, or end-to-end tests, or when the task involves Testing Fundamentals, Unit Testing, Integration Testing, or End-to-End Testing.
test-writer
Write thorough tests following TDD and BDD principles.
quality-performance
Speed, accessibility, and testing bars every delivered app must clear — Core Web Vitals, WCAG 2.2 AA, TDD real-browser E2E, and the build-fail gates.
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…
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.
user-story-writer
Escribir historias de usuario bien estructuradas con criterios de aceptación y casos extremos. Úsalo cuando te pidan escribir historias de usuario, crear tickets a partir de un resumen de características, convertir un PRD en historias o redactar criterios de aceptación. Produce historias listas para estimar en formato…