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 vue-testing-best-practicesgit 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/vue-testing-best-practices)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/vue-testing-best-practices"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/vue-testing-best-practices/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/vue-testing-best-practices"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/vue-testing-best-practices.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.00125 | $0.02918 |
| Opus 5 | $0.00063 | $0.01459 |
| Sonnet 5 | $0.00025 | $0.00584 |
| Haiku 4.5 | $0.00013 | $0.00292 |
Grade A, and why
mk:vue-testing-best-practices 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 6d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue Testing Best Practices
Vue-specific test-design advisor + test-code reviewer. Recommends how to test Vue 3 components, composables, Pinia stores, Vue Router, async/Suspense, Teleport, forms, and accessibility — and audits existing Vitest + Vue Test Utils tests for smells, gaps, and coverage risk. Read-only: it advises and reviews; it never runs, generates, or fixes tests.
This skill is to mk:testing what mk:vue-best-practices is to mk:vue — a
domain-specialized advisory that you invoke deliberately.
When to Use
Invoke-only — this skill does NOT auto-activate. Activate it for:
/mk:vue-testing-best-practices [test file or component](explicit).- "review my Vue tests", "how should I test this component/composable/store", "Vue test best practices", "Vitest or Jest for this Vue app?", "are my async component tests correct?".
Do NOT invoke for (each routes to its owner):
- Running tests / TDD red-green / non-Vue tests / generic Playwright runner protocol →
mk:testing - Diff/PR structural review or test-existence gap detection →
mk:review - Coverage→requirement mapping →
mk:nyquist - QA of a running app + bug fixes →
mk:qa - Generating or running Playwright
.spec.tsE2E →mk:qa-manual - Driving a live browser →
mk:agent-browser/mk:playwright-cli - Writing Vue feature code →
mk:vue/mk:vue-best-practices
Invocation Decision Guide
| You want to… | Use |
|---|---|
| Write/refactor Vue feature code | mk:vue |
| Review Vue feature code / authoring workflow | mk:vue-best-practices |
| Design or review Vue test code; choose test tooling | this skill |
| Actually run tests / TDD loop / non-Vue tests | mk:testing |
| Diff/PR review or "does a test exist for this change?" | mk:review |
| Map test coverage → requirements (which criteria are untested) | mk:nyquist |
| "does the running site work? find + fix bugs" | mk:qa |
| Generate runnable Playwright E2E specs from a spec/URL | mk:qa-manual |
| Drive a real browser | mk:agent-browser / mk:playwright-cli |
What ships with it
16 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.
- reference/accessibility-testing.md 1.9 KB
- reference/async-component-testing.md 4.8 KB
- reference/form-testing.md 3.5 KB
- reference/teleport-testing-complexity.md 4.0 KB
- reference/test-smells-rubric.md 3.8 KB
- reference/testing-async-await-flushpromises.md 5.1 KB
- reference/testing-browser-vs-node-runners.md 5.5 KB
- reference/testing-component-blackbox-approach.md 4.6 KB
- reference/testing-composables-helper-wrapper.md 6.0 KB
- reference/testing-e2e-playwright-recommended.md 6.4 KB
- reference/testing-no-snapshot-only.md 6.1 KB
- reference/testing-pinia-store-setup.md 6.1 KB
- reference/testing-suspense-async-components.md 6.3 KB
- reference/testing-vitest-recommended-for-vue.md 4.9 KB
- reference/vue-router-testing.md 4.0 KB
- SYNC.md 3.3 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.
- 6d ago First seen · 230 lines · 125 tokens per session scan A 320fef0569c1
mk:vue-testing-best-practices is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 125 tokens to every session and 2,918 once invoked, about $0.0006 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
testing-frontend
Use when writing component tests, testing user interactions, mocking APIs, or setting up Vitest/React Testing Library/Vue Test Utils for frontend applications.
storybook-testing
Storybook 10 testing patterns with Vitest integration, ESM-only distribution, CSF3 typesafe factories, play() interaction tests, Chromatic TurboSnap visual regression, module automocking, accessibility addon testing, and autodocs generation. Use when writing component stories, setting up visual regression testing…
vue-component-testing
Applies the three-tier test taxonomy for Vue 3 applications: writes unit tests for composables and Pinia stores with Vitest, component tests for behaviour and user interactions with @testing-library/vue, and acceptance tests for full user flows with Playwright. Ensures tests focus on observable behaviour, not…
Component Test Scaffold (Vue.js)
Generate Vue.js component test skeletons (Vue Test Utils) from specifications.
nextjs-testing
Write Jest or Vitest unit tests with React Testing Library and Playwright E2E tests for Next.js projects. Use when testing components with RTL, mocking APIs with MSW, or creating Playwright user flow tests.
frontend-testing
Comprehensive frontend testing strategy covering unit, integration, E2E, visual regression, and accessibility testing.