integration-testing

integration-testing is a skill for Claude Code, Codex from jnPiyush/AgentX. It costs 36 tokens per session (2,898 once invoked), scanned A, original, Apache-2.0.

A guide to integration tests, which check whether separate parts of a system work together. It covers APIs, databases, services, message queues, authentication, and third-party connections.

In plain words
What is it for?
Use it to test API responses, database queries and migrations, service communication, message producers and consumers, contracts, and external integrations.
Why use it?
It catches errors at the boundaries between components that isolated unit tests cannot see.

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 import { app } from '../../src/app';.

Good fit Use it to test API responses, database queries and migrations, service communication, message producers and consumers, contracts, and external integrations.

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/jnPiyush/AgentX
agentmods
npx agentmods add skills/jnpiyush/agentx/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/jnpiyush/agentx/integration-testing/github.svg)](https://agentmods.dev/skills/jnpiyush/agentx/integration-testing)
Your own site
<a href="https://agentmods.dev/skills/jnpiyush/agentx/integration-testing"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/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/jnpiyush/agentx/integration-testing"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/integration-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,898 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 warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Data Exfiltration · line 283
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 292
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00036 $0.02898
Opus 5.5 $0.00014 $0.01159
Sonnet 5.5 $0.00007 $0.00580
Haiku 4.5 $0.00004 $0.00290

Measured 1mo ago against content hash bc5898f8dba6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

integration-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 1mo 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.

.github/skills/testing/integration-testing/SKILL.md · 431 lines

How it starts

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

Integration Testing

Purpose: Verify that components, services, and systems interact correctly across boundaries. Scope: API testing, contract testing, database integration, service mocking, message queue testing.


When to Use This Skill

  • Testing API endpoints with request/response validation
  • Verifying database queries and migrations
  • Testing service-to-service communication
  • Implementing consumer-driven contract testing
  • Validating message queue producers and consumers
  • Testing authentication and authorization flows
  • Verifying third-party API integrations

When NOT to Use

  • Testing isolated functions or classes (use unit testing)
  • Full user journey testing (use e2e testing)
  • Load/stress testing (use performance testing)

Prerequisites

  • Application with defined service boundaries
  • Docker available for Testcontainers (recommended)
  • API specifications (OpenAPI, AsyncAPI, or similar)

Decision Tree

What integration boundary?
+- HTTP APIs?
|  +- Own API endpoints -> Supertest / httpx / RestAssured
|  +- Third-party APIs -> WireMock / MSW / responses
|  +- Consumer contracts -> Pact / Spring Cloud Contract
+- Database?
|  +- SQL -> Testcontainers + migrations
|  +- NoSQL -> Testcontainers + seed data
|  +- In-memory fallback -> SQLite (unit only, not integration)
+- Message queues?
|  +- Kafka -> Testcontainers kafka
|  +- RabbitMQ -> Testcontainers rabbitmq
|  +- Azure Service Bus -> Emulator or mock
+- External services?
|  +- HTTP-based -> WireMock / MSW
|  +- gRPC -> grpc-mock
|  +- SDK-based -> Interface abstraction + test double
+- Authentication?
|  +- JWT -> Test token generator
|  +- OAuth -> Mock identity provider
|  +- API keys -> Test keys in environment

API Integration Testing

Node.js / Express (Supertest)

// tests/integration/users.api.test.ts
import request from 'supertest';
import { app } from '../../src/app';
import { db } from '../../src/database';

describe('POST /api/users', () => {
  beforeEach(async () => {
    await db.migrate.latest();
    await db.seed.run();
  });

  afterEach(async () => {
    await db('users').truncate();
  });

  it('creates a user and returns 201', async () => {
    const response = await request(app)
      .post('/api/users')
      .send({ name: 'Test User', email: '[email protected]' })
      .set('Authorization', `Bearer ${testToken}`)
      .expect(201);

    expect(response.body).toMatchObject({
      id: expect.any(String),
      name: 'Test User',
      email: '[email protected]',
    });

    // Verify database state
    const user = await db('users').where({ email: '[email protected]' }).first();
    expect(user).toBeDefined();
  });

  it('returns 400 for invalid email', async () => {
    const response = await request(app)
      .post('/api/users')
      .send({ name: 'Test', email: 'not-an-email' })
      .set('Authorization', `Bearer ${testToken}`)
      .expect(400);

    expect(response.body.errors).toContainEqual(
      expect.objectContaining({ field: 'email' })
    );
  });

  it('returns 401 without auth token', async () => {
    await request(app)
      .post('/api/users')
      .send({ name: 'Test', email: '[email protected]' })
      .expect(401);
  });
});

Read the full file on GitHub · 431 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. 1mo ago First seen · 431 lines · 36 tokens per session scan A bc5898f8dba6

Subscribe to this mod's changes

integration-testing is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 36 tokens to every session and 2,898 once invoked, about $0.0001 per session on Opus 5.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

server-side-calls

Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.

trpc/trpc · 61 tokens

mem0-test-integration

Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…

mem0ai/mem0 · 207 tokens

prowler-test-api

Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).

prowler-cloud/prowler · 62 tokens

python-sdk

Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.

ComposioHQ/composio · 60 tokens

convex-test

Generate convex-test tests for the app's Convex functions.

openclaw/clawhub · 16 tokens

voiden

Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.

VoidenHQ/voiden · 28 tokens