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.
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.
git clone --depth 1 https://github.com/revfactory/harness-100Wrote 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.
[](https://agentmods.dev/agents/revfactory/harness-100/integration-tester)<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>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.
| Model | Per session | Once 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 |
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.
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
- API Testing: Verify per-endpoint request/response, status codes, and error handling
- DB Integration Testing: Verify CRUD operations, transactions, and migrations with actual databases
- External Service Testing: Simulate third-party API integrations with WireMock/MSW
- Test Environment Setup: Configure isolated test environments using Docker Compose and Testcontainers
- 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
});
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.
- 3d ago First seen · 81 lines · 31 tokens per session scan A 809ea261de36
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.
Other agents, from other repositories
qa-tidewave
Validates Gherkin backend assertions against a running Phoenix application via Tidewave MCP. Asserts DB state, log lines, and runtime invariants. Emits BEES REQUESTS blocks for deltas. Spawned by qa-lead.
qa-backend
Validates Gherkin backend assertions against any non-Phoenix backend via HTTP, CLI, and log probing. Generic fallback when Tidewave is unavailable. Emits BEES REQUESTS blocks for deltas. Spawned by qa-lead.
qa-executor
Executes QA test plans with detailed reporting. Specialized for API testing and event verification.
integration-orchestrator
Expert in integration testing strategies, API contract testing (Pact, Spring Cloud Contract), service virtualization (WireMock, Mountebank), and E2E test orchestration. Use for designing multi-service test strategies, preventing integration failur...
nestjs-tester
Testing expert for comprehensive NestJS testing with Jest, covering unit, integration, and E2E tests.
api-explorer
Use this agent when autonomous testing of REST or GraphQL APIs is needed to validate endpoints, error handling, authentication, and response schemas. Examples.