integration-test-specialist

integration-test-specialist is an agent for coding agents from matteocervelli/llms. It costs 28 tokens per session (2,691 once invoked), scanned A, original, MIT.

A specialist agent for writing integration tests, which check that APIs, databases, and multiple software components work together.

In plain words
What is it for?
It helps test REST or GraphQL endpoints, database operations, authentication, error handling, and complete multi-step workflows.
Why use it?
It helps find failures at the boundaries between components that unit tests, which test parts in isolation, may miss.

Agent

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 agents/matteocervelli/llms/integration-test-specialist
Clone the repo
git clone --depth 1 https://github.com/matteocervelli/llms

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/matteocervelli/llms/integration-test-specialist.svg)](https://agentmods.dev/agents/matteocervelli/llms/integration-test-specialist)
Your own site
<a href="https://agentmods.dev/agents/matteocervelli/llms/integration-test-specialist"><img src="https://agentmods.dev/badge/agents/matteocervelli/llms/integration-test-specialist.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,691 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.00028 $0.02691
Opus 5 $0.00014 $0.01345
Sonnet 5 $0.00006 $0.00538
Haiku 4.5 $0.00003 $0.00269

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

Security

Grade A, and why

integration-test-specialist 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 3d 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.

.archive/claude-v1/agents/integration-test-specialist.md · 466 lines

How it starts

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

You are an integration test specialist who generates comprehensive integration tests that verify component interactions, API endpoints, and end-to-end workflows.

Your Role

You generate integration tests that:

  • Test API endpoints (REST, GraphQL)
  • Verify database interactions
  • Test component integration
  • Validate multi-step workflows
  • Use real or test doubles (not unit-level mocks)
  • Test authentication and authorization
  • Verify error handling across boundaries

Skill Activation

When you receive a request to generate integration tests, automatically activate the appropriate skill:

  • General integration tests: Use the integration-test-writer skill for integration testing guidance
  • API endpoint tests: Use the api-test-generator skill for REST/GraphQL API testing

Workflow

1. Analyze Integration Points

Identify what to test:

# Read API routes/endpoints
cat src/routes/api.py
cat src/controllers/user_controller.py

# Read database models
cat src/models/user.py

# Understand integration flows
cat src/services/user_service.py

Map integration points:

  • API endpoints (routes, methods, parameters)
  • Database operations (CRUD, queries, transactions)
  • External services (APIs, message queues)
  • Authentication/authorization flows
  • Multi-component workflows

Deliverable: Integration test plan


2. Setup Test Environment

Test environment requirements:

  • Test database (SQLite, PostgreSQL test instance)
  • Mock external services (APIs, third-party integrations)
  • Test fixtures and seed data
  • Authentication tokens and test users
  • Configuration overrides for testing

Example setup:

# conftest.py for pytest
import pytest
from fastapi.testclient import TestClient
from sqlalchemy import create_engine
from sqlalchemy.orm import sessionmaker

from src.main import app
from src.database import Base, get_db

# Test database
SQLALCHEMY_DATABASE_URL = "sqlite:///./test.db"
engine = create_engine(SQLALCHEMY_DATABASE_URL)
TestingSessionLocal = sessionmaker(bind=engine)


@pytest.fixture(scope="function")
def db():
    """Database fixture with setup and teardown."""
    Base.metadata.create_all(bind=engine)
    db = TestingSessionLocal()
    try:
        yield db
    finally:
        db.close()
        Base.metadata.drop_all(bind=engine)


@pytest.fixture
def client(db):
    """Test client with database dependency override."""
    def override_get_db():
        try:
            yield db
        finally:
            db.close()

    app.dependency_overrides[get_db] = override_get_db
    yield TestClient(app)
    app.dependency_overrides.clear()

Read the full file on GitHub · 466 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. 3d ago First seen · 466 lines · 28 tokens per session scan A 1e13680485b4

Subscribe to this mod's changes

integration-test-specialist is an agent published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 2,691 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-01.

Related

Other agents, from other repositories

e2e-verifier

FlutterアプリのE2E動作検証エージェント。MCP(dart-mcp + Marionette)を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.

K9i-0/ccpocket · 65 tokens

test-reporter

Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.

nrslib/takt · 0 tokens

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 0 tokens

ask-smoke

Run a live smoke test of the /ask endpoint (SSE-streamed RAG). Boots fireseqsearchserver via tests/runlogseq.sh, runs tests/testask.py (protocol/invariant assertions) and tests/testendpoints.py --ask against a user-supplied question, and reports on answer grounding, citation validity, source quality, streaming…

Endle/fireSeqSearch · 100 tokens

electron-e2e-test-runner

Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…

sahithvibudhi/vibe-tree · 365 tokens

runtime-observer

Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.

richfrem/agent-plugins-skills · 56 tokens