integration-testing

integration-testing is a skill for Claude Code, Codex from williamzujkowski/standards. It costs 37 tokens per session (3,264 once invoked), scanned B, original, MIT.

A guide to testing how application parts work together, including APIs, databases, and separate services. It covers containers, test doubles, and checks that services follow agreed interfaces.

In plain words
What is it for?
Use it to test real HTTP requests, database migrations, service-to-service communication, and external-service integrations. It also helps set up Docker-based test dependencies and contract tests between services.
Why use it?
It helps find failures that unit tests, which test small pieces in isolation, cannot see. It also provides repeatable test environments and guidance for running these checks in automated builds.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is const app = require('../src/app');.

Good fit Use it to test real HTTP requests, database migrations, service-to-service communication, and external-service integrations. It also helps set up Docker-based test dependencies and contract tests between services.

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/williamzujkowski/standards
agentmods
npx agentmods add skills/williamzujkowski/standards/integration-testing

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 integration-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/williamzujkowski/standards/integration-testing/github.svg)](https://agentmods.dev/skills/williamzujkowski/standards/integration-testing)
Your own site
<a href="https://agentmods.dev/skills/williamzujkowski/standards/integration-testing"><img src="https://agentmods.dev/badge/skills/williamzujkowski/standards/integration-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.

agentmods 80×15 button for integration-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/williamzujkowski/standards/integration-testing"><img src="https://agentmods.dev/badge/skills/williamzujkowski/standards/integration-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,264 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00037 $0.03264
Opus 5.5 $0.00015 $0.01306
Sonnet 5.5 $0.00007 $0.00653
Haiku 4.5 $0.00004 $0.00326

Measured yesterday against content hash a0789080da45, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-30, from the pricing page.

Security

Grade B, and why

integration-testing scanned grade B with 2 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 yesterday.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/setup-test-db.sh, templates/api-test-template.js, templates/integration-test-python.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

response = requests.post('http://localhost:8000/api/users', json=user_data)

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

response = requests.post('http://localhost:8000/api/users', json=user_data)
skills/testing/integration-testing/SKILL.md · 525 lines

How it starts

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

Integration Testing Standards

Quick Navigation: Level 1: Quick Start (5 min) → Level 2: Implementation (30 min) → Level 3: Mastery (Extended)


Level 1: Quick Start (<2,000 tokens, 5 minutes)

Core Principles

  1. Test Real Interactions: Verify actual communication between components
  2. Isolated Environments: Use Docker containers for reproducible tests
  3. Fast Feedback: Keep integration tests under 30 seconds when possible
  4. Contract Testing: Verify API contracts between services
  5. Database Testing: Test with real databases, not mocks

Essential Checklist

  • Testcontainers: Docker-based test dependencies (database, cache, message queue)
  • API testing: REST/GraphQL endpoints tested with real HTTP
  • Database migrations: Test schema migrations and rollbacks
  • Contract tests: Provider-consumer contract verification
  • Test data management: Fixtures and cleanup strategies
  • Service mocking: External services mocked with WireMock/MockServer
  • Docker Compose: Test environment orchestration
  • CI integration: Tests run in isolated containers

Quick Example

# pytest integration test with Testcontainers
import pytest
from testcontainers.postgres import PostgresContainer
from sqlalchemy import create_engine
import requests

@pytest.fixture(scope="module")
def postgres_container():
    """Start PostgreSQL container for testing."""
    with PostgresContainer("postgres:16") as postgres:
        yield postgres

@pytest.fixture
def db_engine(postgres_container):
    """Create database engine with test container."""
    connection_url = postgres_container.get_connection_url()
    engine = create_engine(connection_url)
    # Run migrations
    run_migrations(engine)
    yield engine
    engine.dispose()

def test_create_user_integration(db_engine):
    """Test user creation with real database."""
    # Arrange
    user_data = {'email': '[email protected]', 'name': 'Test User'}

    # Act
    response = requests.post('http://localhost:8000/api/users', json=user_data)

    # Assert
    assert response.status_code == 201
    user_id = response.json()['id']

    # Verify in database
    with db_engine.connect() as conn:
        result = conn.execute("SELECT * FROM users WHERE id = %s", (user_id,))
        user = result.fetchone()
        assert user['email'] == '[email protected]'

Read the full file on GitHub · 525 lines

Files

What ships with it

8 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. yesterday First seen · 525 lines · 37 tokens per session scan B a0789080da45

Subscribe to this mod's changes

integration-testing is a skill published in the GitHub repository williamzujkowski/standards (18 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 3,264 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-29.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens