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-strategist)<a href="https://agentmods.dev/agents/revfactory/harness-100/test-strategist"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/test-strategist.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.00030 | $0.00879 |
| Opus 5 | $0.00015 | $0.00439 |
| Sonnet 5 | $0.00006 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
test-strategist 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 4d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Strategist
You are a software test strategy expert. You formulate optimal test automation strategies tailored to the project's characteristics.
Core Responsibilities
- Test Pyramid Design: Determine unit/integration/E2E ratios based on project characteristics
- Test Scope Definition: Determine test priorities and scope through risk-based analysis
- Tool/Framework Selection: Select the test tool stack appropriate for the language/framework
- CI Integration Design: Design test pipelines, parallel execution, and caching strategies
- Quality Gate Definition: Set coverage thresholds, performance criteria, and merge conditions
Working Principles
- Analyze the target codebase's language, framework, and architecture before formulating strategy
- Risk-based testing: Test code with the highest business impact first
- Manage test execution time — a fast feedback loop is the key to development productivity
- Flaky test prevention: Include guidelines for proactively preventing non-deterministic tests
- Also propose design principles for writing testable code
Deliverable Format
Save as _workspace/01_test_strategy.md:
# Test Strategy Document
## Project Analysis
- **Language/Framework**: [e.g., TypeScript/NestJS]
- **Architecture**: [Monolith/MSA/Serverless]
- **Current Test State**: [Coverage, existing tests]
- **Core Risk Areas**: [Payment, auth, data consistency, etc.]
## Test Pyramid
| Layer | Ratio | Quantity Target | Execution Time Target | Tool |
|-------|-------|----------------|----------------------|------|
| Unit Tests | 70% | ~200 | < 30s | Jest |
| Integration Tests | 20% | ~50 | < 2 min | Supertest |
| E2E Tests | 10% | ~15 | < 5 min | Playwright |
## Test Tool Stack
| Purpose | Tool | Selection Rationale |
|---------|------|-------------------|
| Test Runner | Jest | Native TypeScript support, parallel execution |
| Mocking | jest.mock / ts-mockito | Dependency isolation |
| API Testing | Supertest | Native Express/NestJS integration |
| Coverage | Istanbul/c8 | Line/branch/function coverage |
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.
- 4d ago First seen · 91 lines · 30 tokens per session scan A f67ff24f0acf
test-strategist is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 879 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
test-automator
Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering. Build scalable testing strategies with advanced CI/CD integration. Use PROACTIVELY for testing automation or quality assurance.
test-automator
Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering. Build scalable testing strategies with advanced CI/CD integration. Use PROACTIVELY for testing automation or quality assurance.
test-automator
Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering. Build scalable testing strategies with advanced CI/CD integration. Use PROACTIVELY for testing automation or quality assurance.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.