Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/AratKruglik/claude-sdlcnpx agentmods add skills/aratkruglik/claude-sdlc/vue-testingWrote 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/aratkruglik/claude-sdlc/vue-testing)<a href="https://agentmods.dev/skills/aratkruglik/claude-sdlc/vue-testing"><img src="https://agentmods.dev/badge/skills/aratkruglik/claude-sdlc/vue-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/aratkruglik/claude-sdlc/vue-testing"><img src="https://agentmods.dev/badge/skills/aratkruglik/claude-sdlc/vue-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00155 | $0.03473 |
| Opus 5 | $0.00077 | $0.01736 |
| Sonnet 5 | $0.00031 | $0.00695 |
| Haiku 4.5 | $0.00015 | $0.00347 |
Grade A, and why
vue-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 8d 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 — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue 3 Testing Patterns
Test framework selection
| Layer | Framework |
|---|---|
| Component, composable, plain TS unit | Vitest + @vue/test-utils (preferred for Vite projects) |
| Component (alt) | @testing-library/vue (RTL-style API) |
| Component in browser | Cypress component testing (slower, more realistic) |
| End-to-end | Playwright (preferred) or Cypress |
For Vue 3 + Vite, Vitest is the modern default. Match what's installed.
Vitest setup
vite.config.ts:
import { defineConfig } from 'vitest/config';
import vue from '@vitejs/plugin-vue';
import path from 'path';
export default defineConfig({
plugins: [vue()],
test: {
environment: 'jsdom',
globals: true,
setupFiles: ['./vitest.setup.ts'],
coverage: {
reporter: ['text', 'html'],
exclude: ['**/*.config.*', '**/*.spec.*', 'src/main.ts'],
},
},
resolve: {
alias: { '@': path.resolve(__dirname, './src') },
},
});
vitest.setup.ts:
// Add custom matchers if needed
import { afterEach } from 'vitest';
import { config } from '@vue/test-utils';
afterEach(() => {
// cleanup mounted components
});
// Stub global components if needed
config.global.stubs = {
RouterLink: true,
RouterView: true,
};
Install: pnpm add -D vitest @vue/test-utils @vitejs/plugin-vue jsdom.
mount vs shallowMount
import { mount, shallowMount } from '@vue/test-utils';
// mount renders ALL children real
const wrapper = mount(MyComponent, { props: { name: 'Alice' } });
// shallowMount stubs ALL child components (renders <ChildComponent-stub />)
const wrapper = shallowMount(MyComponent, { props: { name: 'Alice' } });
Prefer mount — catches integration bugs (prop passing, slot rendering). Use shallowMount only for very large component trees where rendering full subtrees is slow.
Component test (basics)
// src/components/UserCard.spec.ts
import { describe, it, expect, vi } from 'vitest';
import { mount } from '@vue/test-utils';
import UserCard from './UserCard.vue';
describe('UserCard', () => {
it('renders user name and email', () => {
const wrapper = mount(UserCard, {
props: { user: { id: '1', name: 'Alice', email: '[email protected]' } },
});
expect(wrapper.text()).toContain('Alice');
expect(wrapper.text()).toContain('[email protected]');
});
it('emits "delete" when delete button clicked', async () => {
const wrapper = mount(UserCard, {
props: { user: { id: '1', name: 'Alice', email: '[email protected]' } },
});
await wrapper.find('[data-testid="delete-btn"]').trigger('click');
expect(wrapper.emitted('delete')).toEqual([['1']]);
});
it('renders header slot when provided', () => {
const wrapper = mount(UserCard, {
props: { user: { id: '1', name: 'Alice', email: '[email protected]' } },
slots: { header: '<h2>Custom Header</h2>' },
});
expect(wrapper.find('h2').text()).toBe('Custom Header');
});
});
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.
- 8d ago First seen · 470 lines · 155 tokens per session scan A a0478bddcf57
vue-testing is a skill published in the GitHub repository AratKruglik/claude-sdlc (33 stars, last pushed 6d ago), licensed MIT. It adds 155 tokens to every session and 3,473 once invoked, about $0.0008 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
frontend-testing
Comprehensive frontend testing strategy covering unit, integration, E2E, visual regression, and accessibility testing.
test-implement
Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.
angular-testing
Write unit and integration tests for Angular v20+ applications using Vitest or Jasmine with TestBed and modern testing patterns. Use for testing components with signals, OnPush change detection, services with inject(), and HTTP interactions. Triggers on test creation, testing signal-based components, mocking…
react-testing-workflows
Testing strategy and execution for React applications. Covers Vitest configuration, React Testing Library patterns, custom hook testing, Playwright E2E, Storybook stories and play functions, and coverage reporting. Keywords: test, vitest, testing library, playwright, storybook, coverage, unit test, integration test…
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…
frontend-testing
Scaffold and advise on frontend testing for production readiness, mapped to the Front-End-Checklist Testing category (13 rules). Defines a testing pyramid (unit, integration, E2E, visual, a11y, cross-browser, real-device, perf-budget, mutation, error-monitoring, coverage, mocking, contract) and emits copy-pasteable…