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 soulcodex/agentic --skill vue-component-testinggit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/vue-component-testing)<a href="https://agentmods.dev/skills/soulcodex/agentic/vue-component-testing"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/vue-component-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/soulcodex/agentic/vue-component-testing"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/vue-component-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.00079 | $0.01132 |
| Opus 5.5 | $0.00032 | $0.00453 |
| Sonnet 5.5 | $0.00016 | $0.00226 |
| Haiku 4.5 | $0.00008 | $0.00113 |
Grade A, and why
vue-component-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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue Component Testing Skill
Step 1 — Classify What Needs to Be Tested
For each piece of code, assign a test tier:
- Composable / store action / pure function → Unit test (Vitest, no DOM)
- Component behaviour / user interaction / emitted events → Component test (@testing-library/vue + Vitest)
- User flow across pages / real navigation → E2E (Playwright)
List all files in scope and assign each a tier before writing any tests.
Step 2 — Write Unit Tests (Composables and Stores)
- Composable: import and call directly, assert returned refs/computed values. Use
setActivePinia(createPinia())inbeforeEachif the composable accesses a store. - Store:
setActivePinia(createPinia())inbeforeEach, call actions directly, assert state. Test getters by patching state. - No DOM, no component mounting — pure JS/TS only.
import { setActivePinia, createPinia } from 'pinia'
import { beforeEach, describe, expect, it } from 'vitest'
import { useAuthStore } from './auth.store'
let store: ReturnType<typeof useAuthStore>
beforeEach(() => { setActivePinia(createPinia()); store = useAuthStore() })
it('login sets user', async () => {
await store.login({ email: '[email protected]', password: 'secret' })
expect(store.user).not.toBeNull()
})
Step 3 — Write Component Tests
- Use
@testing-library/vuefor user-centric assertions:getByRole,findByText,userEvent. - Use
@vue/test-utilswhen asserting emitted events, inspecting component output, or working with slots. - Use
createTestingPinia()from@pinia/testingto stub store actions. - Mount the real component (not shallow) unless the child is a heavy external library.
- Assert: what the user sees (text, roles, visibility), which events are emitted, which store actions are called.
- Do NOT assert: internal refs, CSS classes, snapshot blobs.
- In TypeScript projects, keep TS/JS imports ESM-only and use aliases for cross-directory imports.
import { render, screen, fireEvent } from '@testing-library/vue'
import { createTestingPinia } from '@pinia/testing'
import { describe, expect, it, vi } from 'vitest'
import BaseButton from '<alias>/components/BaseButton.vue'
const mockTrack = vi.fn()
vi.mock('<alias>/lib/analytics', () => ({ trackEvent: mockTrack }))
it('tracks click event on button press', async () => {
render(BaseButton, {
props: { label: 'Save' },
global: { plugins: [createTestingPinia()] },
})
await fireEvent.click(screen.getByRole('button', { name: 'Save' }))
expect(mockTrack).toHaveBeenCalledWith('button_click', expect.any(Object))
})
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 · 114 lines · 79 tokens per session scan A 710f230440e1
vue-component-testing is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 1,132 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-08-31.
Other skills, from other repositories
test-generator
Generate comprehensive unit, integration, and end-to-end tests. Use when adding test coverage, writing tests for new features, or improving existing test suites.
test-agent
You are the Test agent for this project. You own unit, component, integration, and E2E tests, plus test fixtures and test infrastructure.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.
tmux-real-user-testing
A real-user test workflow for Qwen Code's terminal interface, using tmux to drive the program and capture readable screen snapshots. tmux is a tool for running and observing terminal sessions.
agent-reproduce-align
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.