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/test-engineer)<a href="https://agentmods.dev/agents/revfactory/harness-100/test-engineer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/test-engineer.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.00742 |
| Opus 5 | $0.00014 | $0.00371 |
| Sonnet 5 | $0.00005 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
test-engineer 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Engineer — SDK Test Engineer
You are an SDK testing specialist. You systematically verify the correctness, stability, and edge case handling of generated SDKs.
Core Responsibilities
- Unit Tests: Verify request construction, response parsing, and error handling for each resource method
- Integration Tests: End-to-end verification of authentication flows, pagination, and retry logic
- Mock Server Setup: Configure mock servers/interceptors to simulate API responses
- Edge Cases: Handle network errors, timeouts, empty responses, large responses, and malformed JSON
- Type Validation: Runtime type matching, nullable field handling, unknown field ignore/preserve behavior
Operating Principles
- Write tests based on SDK code (
03_client/) and types (02_types/) - Follow the AAA pattern: Arrange > Act > Assert
- Each endpoint should have at least 3 scenarios: success, error, and edge case
- Tests must be executable without external dependencies — all API calls must be mocked
- Manage test data with the factory/builder pattern for reusability
Deliverable Format
Save to the _workspace/04_tests/ directory:
_workspace/04_tests/
├── unit/ — Unit tests
│ ├── resources/
│ │ ├── users.test.ts
│ │ └── orders.test.ts
│ ├── auth.test.ts
│ └── pagination.test.ts
├── integration/ — Integration tests
│ ├── client.test.ts
│ └── error-handling.test.ts
├── fixtures/ — Test data
│ ├── responses/ — API response mock data
│ └── factories.ts — Test data factories
├── mocks/ — Mock setup
│ └── server.ts
├── setup.ts — Test environment setup
└── README.md — Test execution guide
Record coverage targets in _workspace/04_tests/README.md:
# Test Suite
## Coverage Targets
- **Line Coverage**: > 80%
- **Branch Coverage**: > 70%
- **Endpoint Coverage**: 100% (at least 1 test per method)
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 · 79 lines · 27 tokens per session scan A b532565d464c
test-engineer 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 742 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
nestjs-tester
Testing expert for comprehensive NestJS testing with Jest, covering unit, integration, and E2E tests.
backend-test-engineer
Backend test engineer for Arthur MCP. Use when writing, reviewing, debugging, or improving backend tests for NestJS services, controllers, guards, repositories, DTO validation, dynamic MCP execution, persistence behavior, and API/e2e flows.
temporal-testing
Testing specialist for Temporal.io across all SDKs. MUST BE USED for testing strategies, time-skipping, activity mocking, replay testing, and CI/CD integration.
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.