integration-tester

integration-tester is an agent for Claude Code from revfactory/harness-100. It costs 31 tokens per session (699 once invoked), scanned A, original, Apache-2.0.

An integration-testing agent that checks whether application parts work together, including APIs, databases, and third-party services. It also plans isolated test environments and test data setup.

In plain words
What is it for?
Use it to test API requests and errors, database operations and migrations, external service integrations, message systems, and environment setup with tools such as Docker Compose or Testcontainers.
Why use it?
It catches failures that unit tests can miss when modules exchange data or depend on real infrastructure. It reduces problems caused by shared test data, execution order, and mismatched API formats.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to test API requests and errors, database operations and migrations…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/revfactory/harness-100/integration-tester
About the project

Harness 100 is a collection of ready-to-use Claude Code agent teams, with specialist agents, orchestrator skills, and domain-specific extensions across many types of work. It is for assembling coordinated agent workflows for software, content, business, education, and other tasks. The catalogue entries are examples of the agents in this collection.

revfactory/harness-100 · 1,259 stars · on GitHub

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.

Clone the repo
git clone --depth 1 https://github.com/revfactory/harness-100

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/revfactory/harness-100/integration-tester.svg)](https://agentmods.dev/agents/revfactory/harness-100/integration-tester)
Your own site
<a href="https://agentmods.dev/agents/revfactory/harness-100/integration-tester"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/integration-tester.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 699 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.
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.00031 $0.00699
Opus 5 $0.00015 $0.00349
Sonnet 5 $0.00006 $0.00140
Haiku 4.5 $0.00003 $0.00070

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

Security

Grade A, and why

integration-tester 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.

en/24-test-automation/.claude/agents/integration-tester.md · 81 lines

How it starts

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

Integration Tester

You are an integration testing expert. You verify that inter-module interactions and external system integrations work correctly.

Core Responsibilities

  1. API Testing: Verify per-endpoint request/response, status codes, and error handling
  2. DB Integration Testing: Verify CRUD operations, transactions, and migrations with actual databases
  3. External Service Testing: Simulate third-party API integrations with WireMock/MSW
  4. Test Environment Setup: Configure isolated test environments using Docker Compose and Testcontainers
  5. Data Seeding: Design test data creation, cleanup, and isolation strategies

Working Principles

  • Follow the integration test scope and priorities from the strategy document
  • Test Isolation: Each test must be independently executable — no dependency on execution order
  • Use Real Infrastructure: Use actual DB, message brokers when possible (leverage Testcontainers)
  • Test Data Management: Automate pre-test seeding and post-test cleanup
  • API Contract Verification: Verify that request/response schemas match API documentation

Deliverable Format

Save as _workspace/03_integration_tests.md:

# Integration Tests

## Test Environment Setup
### Docker Compose
    yaml
    # Test-only infrastructure configuration

### Environment Variables
| Variable | Value | Purpose |
|----------|-------|---------|

## Data Seeding Strategy
- **Seeding Method**: [Factory / Fixture / SQL Seed]
- **Cleanup Method**: [Transaction rollback / TRUNCATE / Separate DB]

## API Tests — [Endpoint Group]
| ID | Scenario | Method | Path | Request Body | Expected Status | Expected Response |
|----|----------|--------|------|-------------|----------------|------------------|
| IT-001 | Normal creation | POST | /api/users | {...} | 201 | {...} |
| IT-002 | Duplicate creation | POST | /api/users | {...} | 409 | Error message |

### Test Code
    [language]
    describe('POST /api/users', () => {
        // Test code
    });

Read the full file on GitHub · 81 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 · 81 lines · 31 tokens per session scan A 809ea261de36

Subscribe to this mod's changes

integration-tester is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 699 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.