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 agentmods add skills/soulcodex/agentic/vue-component-testingnpx skills add soulcodex/agentic --skill vue-component-testinggit clone --depth 1 https://github.com/soulcodex/agenticWhat 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 | $0.00079 | $0.01132 |
| Opus 5 | $0.00039 | $0.00566 |
| Sonnet 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 2d 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.
- 2d 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 2d ago), licensed MIT. It adds 79 tokens to every session and 1,132 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
zoning-envelope
Generate interactive 3D zoning envelope viewers from zoning analysis reports. Use when the user asks to "visualize the zoning envelope" or see buildable massing in 3D, typically after /as:zoning-analysis-nyc. Requires a zoning analysis report as input.
authoring-components
Guide for creating new Elements components with all required files, base classes, metadata patterns, and test boilerplate. Use this skill whenever the user wants to create, scaffold, or set up a new component from scratch, needs to understand the required 10-file structure, asks about base classes and mixins…
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
opencli-usage
Use at the start of any OpenCLI session — this is the top-level map of what opencli can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".
opencli-browser-sitemap
Use when driving a website with opencli browser and sitemap context is available, requested, or needed to avoid blind navigation. Guides agents to consume site sitemap files lazily, choose adapter/browser fallback paths, resume from state signatures, and mark stale sitemap entries without trusting them over live…
nuxt-ui
Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.