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/notque/vexjoy-agent/vitest-runnernpx skills add notque/vexjoy-agent --skill vitest-runnergit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/vitest-runner)<a href="https://agentmods.dev/skills/notque/vexjoy-agent/vitest-runner"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/vitest-runner.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00644 |
| Opus 5 | $0.00008 | $0.00322 |
| Sonnet 5 | $0.00003 | $0.00129 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
vitest-runner 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 today.
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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vitest runner
Run existing Vitest tests and report results. A check-only request does not authorize changing tests, assertions, dependencies, or configuration.
Run
Read repository instructions and package scripts. Check package.json, vitest.config.*, and vite.config.* to confirm Vitest and its test configuration. Use the installed project version; avoid implicit npx downloads. If Vitest is unavailable, report setup needed rather than installing it.
Use the repository test command or these defaults. Always use run; bare vitest can enter watch mode.
| Scope | Command |
|---|---|
| Whole configured suite | npx vitest run --reporter=verbose 2>&1 |
| File or directory | npx vitest run path/to/test.ts 2>&1 |
| Test-name pattern | npx vitest run -t "pattern" 2>&1 |
| Requested coverage | npx vitest run --coverage 2>&1 |
Capture the process exit code and full output. Report pass/fail, checked scope, passed/failed/skipped counts, and duration. For failures retain the file, full test name, assertion difference, and relevant stack location. Keep complete logs available; show useful excerpts instead of every passing test. Nonzero exit is failure, including discovery or tool failures; partial output is not a passing run.
Recovery
- Vitest missing/node_modules absent: inspect dependencies. Setup may require
npm installornpm install -D vitest; use the repository package manager during authorized setup. - No test files: check file naming (
*.test.ts,*.spec.ts,*.test.js) and configured include/exclude globs. Report discovery failure; do not change config to mask it. - Missing DOM environment: inspect
environmentforjsdomorhappy-dom. Suggest the matching devDependency (npm install -D jsdomornpm install -D happy-dom);@testing-library/jest-domadds matchers, not an environment. - Out of memory: diagnose with directory batches such as
npx vitest run src/unit/,--pool=forks, or--shard=1/Nwhen supported by the installed version. A full-suite claim requires all batches/shards; a diagnostic subset is not full verification. - Failing assertions: report the mismatch. When fixing is authorized, determine whether implementation or test is wrong; never weaken assertions merely to make the run green.
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.
- today Changed · -98 lines 32b52725f687
- yesterday First seen · 148 lines · 16 tokens per session scan A 801cd7d823ca
vitest-runner is a skill published in the GitHub repository notque/vexjoy-agent (420 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 644 once invoked, about $0.0001 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
adk
Use this skill when you've got questions about the Botpress Agent Development Kit (ADK) - like when you're building a feature that involves tables, actions, tools, workflows, conversations, files, knowledge bases, triggers, or Zai.
typescript-patterns
TypeScript types: generics, discriminated unions, Zod, satisfies, branded types. Triggers: TypeScript, TS, generics, Zod, satisfies, strict mode.
typescript-rules
TypeScript/JavaScript coding rules: style, patterns, security, testing. Triggers: .ts, .tsx, .js, .jsx, package.json, tsconfig.json, React, Next.js, Vue, Vite, Vitest, Jest, ESLint.
valibot
Repository guidance for using Valibot as the schema validation library within the hr-skills monorepo. Use when writing or modifying schemas in packages/hr-skills-ref/src/schema.ts or packages/hr-skills-build/src/shared/schema.ts, when validating parsed YAML frontmatter, when handling safeParse results, or when…
typescript
Repository guidance for writing, reviewing, and maintaining TypeScript code within the hr-skills monorepo. Covers project conventions, compiler settings, module structure, and development workflows.
ai-provider-anthropic-sdk
Official Anthropic SDK patterns for TypeScript/Node.js — client setup, Messages API, streaming, tool use, vision, extended thinking, structured outputs, prompt caching, batch API, and production best practices.