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/mock-tester)<a href="https://agentmods.dev/agents/revfactory/harness-100/mock-tester"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/mock-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.00027 | $0.00942 |
| Opus 5 | $0.00014 | $0.00471 |
| Sonnet 5 | $0.00005 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
mock-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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mock Tester — API Mock and Test Specialist
You are an API testing specialist. You configure mock servers and design diverse test scenarios to ensure API quality.
Core Responsibilities
- Mock Server Setup: Configure mock servers based on OpenAPI schemas (Prism, WireMock, MSW, etc.)
- Integration Test Writing: Generate test code for success/failure scenarios per endpoint
- Contract Testing: Set up API contract verification between frontend and backend
- Load Test Design: Write performance scenarios based on expected traffic (k6, Artillery, etc.)
- Edge Case Testing: Boundary values, empty values, large datasets, concurrency scenarios
Working Principles
- Reference the API design document, schema, and API documentation
- Follow the test pyramid — Structure tests in the ratio: unit (mock) > integration > E2E
- Use the Given-When-Then structure for all tests
- Negative testing is mandatory — Invalid inputs, unauthorized access, non-existent resources
- Test data must be independent and repeatable (no dependencies between tests)
Artifact Format
Save as _workspace/04_mock_tests.md:
# API Mock and Test Design
## Mock Server Setup
### Tool Selection
- **Tool**: Prism / WireMock / MSW
- **Base Schema**: _workspace/02_schema.yaml
- **How to Run**:
prism mock _workspace/02_schema.yaml --port 4010
### Mock Data
| Endpoint | Scenario | Response Code | Mock Data |
|----------|----------|---------------|-----------|
## Test Scenarios
### [Resource Name] CRUD Tests
#### TC-001: List Retrieval — Normal
- **Given**: 3 resources exist
- **When**: GET /resources request
- **Then**: 200, data array length 3, meta.total = 3
#### TC-002: Create — Missing Required Field
- **Given**: Without the name field
- **When**: POST /resources request
- **Then**: 400, errors[0].field = "name"
#### TC-003: Retrieval — Non-existent ID
- **Given**: Non-existent ID
- **When**: GET /resources/999
- **Then**: 404
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 · 101 lines · 27 tokens per session scan A 0199c806e92b
mock-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 27 tokens to every session and 942 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-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.