test-levels

test-levels is a skill for Claude Code from georgekhananaev/claude-skills-vault. It costs 46 tokens per session (1,675 once invoked), scanned A, original, MIT.

A guide to three levels of software testing: unit tests for small pieces of code, integration tests for connected parts, and end-to-end tests for complete user flows. It uses a car-building analogy and includes Playwright examples.

In plain words
What is it for?
Use it to explain testing to a team, decide which tests to write, review coverage, or onboard developers who are new to testing.
Why use it?
It helps developers understand what each test level checks and choose tests that match the size and purpose of a change.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import {mockLoggedUser} from '../../common';.

Good fit Use it to explain testing to a team, decide which tests to write, review coverage, or onboard developers who are new to testing.

Compare 6 skills from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/georgekhananaev/claude-skills-vault
agentmods
npx agentmods add skills/georgekhananaev/claude-skills-vault/test-levels

Made for: Claude Code.

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 test-levels

README.md
[![agentmods](https://agentmods.dev/badge/skills/georgekhananaev/claude-skills-vault/test-levels/github.svg)](https://agentmods.dev/skills/georgekhananaev/claude-skills-vault/test-levels)
Your own site
<a href="https://agentmods.dev/skills/georgekhananaev/claude-skills-vault/test-levels"><img src="https://agentmods.dev/badge/skills/georgekhananaev/claude-skills-vault/test-levels/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.

agentmods 80×15 button for test-levels

Your own site · 80×15
<a href="https://agentmods.dev/skills/georgekhananaev/claude-skills-vault/test-levels"><img src="https://agentmods.dev/badge/skills/georgekhananaev/claude-skills-vault/test-levels.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,675 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00046 $0.01675
Opus 5 $0.00023 $0.00838
Sonnet 5 $0.00009 $0.00335
Haiku 4.5 $0.00005 $0.00168

Measured 8d ago against content hash 3ef7d98b8bbc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

test-levels 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.

.claude/skills/test-levels/SKILL.md · 251 lines

How it starts

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

Test Levels Guide

Explains test types & guides test selection using car analogy.

When to Use

Invoke when:

  • Explaining test concepts to team members
  • Deciding which test type to write
  • Reviewing test coverage strategy
  • Onboarding new developers to testing

The 3 Test Levels

1. Unit Test (Test Case)

The specific instruction.

Single fn/component tested in isolation. No external deps (DB, API, browser).

Aspect Description
Analogy "Check if left turn signal blinks when I push lever down"
Scope Tiny detail - one fn, one input/output
Speed Fast (ms)
Location tests/unit/

When to write:

  • Pure functions (formatters, validators, utils)
  • Data transformations
  • Business logic w/o side effects

Project example:

// tests/unit/utils/formatters.spec.ts
import {expect, test} from 'next/experimental/testmode/playwright';
import {leadingZero, formatCurrency} from '@/app/_utils/formatters';

test.describe('formatters', () => {
    test('leadingZero adds zero to single-digit numbers', () => {
        expect(leadingZero(7)).toBe('07');
        expect(leadingZero(10)).toBe('10');
    });

    test('formatCurrency formats correctly', () => {
        const result = formatCurrency({value: 1234.56, locale: 'en', currency: 'USD'});
        expect(result).toBe('1,234.56 $');
    });
});

2. Integration Test

The handshake.

Tests if 2+ parts communicate correctly. Focuses on connections, not full system.

Aspect Description
Analogy "Does engine make wheels turn?" (Engine → Transmission)
Scope Connections between components
Speed Medium (100ms-few seconds)
Location tests/integration/

When to write:

  • Validators w/ schemas (Zod)
  • API route handlers
  • Service-to-service communication
  • DB queries w/ mocked data

Project example:

Read the full file on GitHub · 251 lines

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. 8d ago First seen · 251 lines · 46 tokens per session scan A 3ef7d98b8bbc

Subscribe to this mod's changes

test-levels is a skill published in the GitHub repository georgekhananaev/claude-skills-vault (28 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,675 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

req-to-test

Generates comprehensive test scenarios from requirements including BDD/Gherkin scenarios, unit tests, integration tests, and end-to-end test cases. Use when converting requirements, user stories, or specifications into testable scenarios with full coverage including happy paths, error cases, edge cases, and boundary…

ArabelaTso/Skills-4-SE · 71 tokens

test-strategy

Use when deciding what to test and at which level. Covers the test pyramid, what belongs in unit versus integration versus end-to-end tests, coverage as a signal rather than a target, and eliminating flakiness.

nimadorostkar/Claude-Skills-collection · 47 tokens

writing-tests

Write unit, integration, and E2E tests that follow the testing pyramid, the Arrange-Act-Assert pattern, the shouldXwhenY naming convention, and meet a 75% (target 80%) branch coverage gate per supported OS. Use when the user asks to write tests, add coverage, build a test suite, fix flaky tests, or verify a feature…

Cristhianzl/claude-skills-czl · 103 tokens

test-strategy-document

Create a production-ready Testing Strategy and QA Execution Plan. Covers testing levels (unit, integration, E2E, performance), mocking boundaries, test environment matrix, code coverage thresholds, and automated CI pipeline runsheets. Use when establishing a QA framework for a new system or feature set.

fattain-naime/engineering-docs · 62 tokens

wp-plugin-testing

Use when writing or setting up tests for a WordPress plugin — PHPUnit integration tests using WPUnitTestCase with the WP test suite (bin/install-wp-tests.sh, phpunit.xml.dist, tests/bootstrap.php), unit tests with Brain Monkey (when() / expect() / Mockery) or WPMock, test factories (factory()->post->create()…

mralaminahamed/wp-dev-skills · 340 tokens

test-writing

Write comprehensive tests for code including unit tests, integration tests, and end-to-end tests. Use this to ensure code quality, catch bugs, and validate functionality.

KarmaloopAI/Jiva · 35 tokens