uvs-test

uvs-test is a skill for Claude Code, Codex from utsavanand/uv-suite. It costs 67 tokens per session (860 once invoked), scanned A, original, MIT.

A testing skill that routes work to a specialist for code tests or AI evaluation tests. TDD means developing with tests that check expected behavior; an AI evaluation checks an AI system’s outputs.

In plain words
What is it for?
Use it for unit tests, integration tests, or evaluations of an AI or language-model feature.
Why use it?
It helps create the right kind of tests after a feature is built, when test coverage is low, or when an AI-powered feature changes.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/utsavanand/uv-suite/uvs-test
Any agent
npx skills add utsavanand/uv-suite --skill uvs-test
Clone the repo
git clone --depth 1 https://github.com/utsavanand/uv-suite

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for uvs-test

README.md
[![agentmods](https://agentmods.dev/badge/skills/utsavanand/uv-suite/uvs-test.svg)](https://agentmods.dev/skills/utsavanand/uv-suite/uvs-test)
Your own site
<a href="https://agentmods.dev/skills/utsavanand/uv-suite/uvs-test"><img src="https://agentmods.dev/badge/skills/utsavanand/uv-suite/uvs-test.svg" alt="Measured on agentmods" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 860 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00067 $0.00860
Opus 5 $0.00034 $0.00430
Sonnet 5 $0.00013 $0.00172
Haiku 4.5 $0.00007 $0.00086

Measured 5d ago against content hash 0e2b43da5896, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

uvs-test 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 5d 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.

skills/uvs-test/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Target

$ARGUMENTS

Mode

The orchestrator picks one specialist per run. Default is --unit.

case "$ARGUMENTS" in
  *--eval*)        echo "MODE=eval        → specialists/eval.md        (eval-writer agent)";;
  *--integration*) echo "MODE=integration → specialists/integration.md (test-writer agent)";;
  *)               echo "MODE=unit        → specialists/unit.md        (test-writer agent)";;
esac

Context for code tests (unit / integration)

Existing test patterns (match these)

!find . \( -name "*.test.*" -o -name "*.spec.*" -o -name "test_*" \) -not -path "*/node_modules/*" 2>/dev/null | head -5

!cat $(find . \( -name "*.test.*" -o -name "*.spec.*" \) -not -path "*/node_modules/*" 2>/dev/null | head -1) 2>/dev/null | head -40 || echo "No existing tests found"

Project test command

!cat package.json 2>/dev/null | grep -A2 '"test"' || echo "No package.json test script"

Context for evals (--eval)

Existing eval framework

!find . \( -name "*eval*" -o -name "*evals*" \) -not -path "*/node_modules/*" 2>/dev/null | head -10 || echo "No eval files found"

Session output directory

Write eval artifacts under this directory (scoped to the current session):

!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-session.sh

Shared prior analysis

Spec (what to test / evaluate against)

!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-best.sh 'specs/*.md' 60 || echo "No spec found — work from code/prompt behavior"

Acts plan (current task context)

!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-best.sh 'architecture/acts-plan.md' 40 || echo "No acts plan found"

Session checkpoint

!cat uv-out/current/checkpoints/latest.md 2>/dev/null | head -40 || echo "No checkpoint"

Dispatch

Read the MODE line above. It names the specialist prompt file and the agent to use:

MODE Specialist prompt Agent
unit skills/uvs-test/specialists/unit.md test-writer
integration skills/uvs-test/specialists/integration.md test-writer
eval skills/uvs-test/specialists/eval.md eval-writer

Read the full file on GitHub · 90 lines

Files

What ships with it

3 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.

Changes

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.

  1. 5d ago First seen · 90 lines · 67 tokens per session scan A 0e2b43da5896

Subscribe to this mod's changes

uvs-test is a skill published in the GitHub repository utsavanand/uv-suite (2 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 860 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens