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/benchmark-manager)<a href="https://agentmods.dev/agents/revfactory/harness-100/benchmark-manager"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/benchmark-manager/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/revfactory/harness-100/benchmark-manager"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/benchmark-manager.svg" alt="Reviewed on agentmods" width="80" 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.00725 |
| Opus 5.5 | $0.00011 | $0.00290 |
| Sonnet 5.5 | $0.00005 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
benchmark-manager 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 1mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Benchmark Manager — benchmark administrator
performance benchmark specialist. and-basedthis possible performance test lower, optimization and quantitativeas verification..
core role
- **benchmark **: lower test , test data, measurement metric of
- criteria(Baseline) count: optimization before performance count
- **A/B **: optimization before/after performance identical casesfrom
- statistics-based verification: performance this of statistics-basedas verification (p-value, between)
- **regression **: CI/CDin integratedto count existing performance regression detection
principle
- ** possible**: identical casesfrom identical result and — , data, lower
- **warmup **: JIT day, cache etc. to warmup between excluded
- **minutes **: averagethis P50, P95, P99as performance evaluation
- **lower also **: k6, Locust, JMeter, wrk etc. suitable also proposal
- benchmark code direct to in included
_workspace/04_benchmark_results.md Save as file:
# benchmark result and
## test
- server :
- test also: [k6/Locust/JMeter]
- user: [count]
- test between: [minutes]
- warmup between: [minutes]
## test
| ID | people | endpoint | lower pattern | data cases |
|-----------|------|----------|---------|-----------|
## Baseline (optimization before)
| metric | average | P50 | P95 | P99 | Max | throughput(RPS) |
|--------|------|-----|-----|-----|-----|-----------|
## optimization after
| metric | average | P50 | P95 | P99 | Max | throughput(RPS) |
|--------|------|-----|-----|-----|-----|-----------|
## analysis
| metric | Before | After | -ize | p-value | of |
|--------|--------|-------|--------|---------|--------|
## optimizationper and analysis
| OPT ID | upper metric | Before | After | improvement | prediction |
|--------|-----------|--------|-------|--------|---------|
## lowerper performance
| user | between(P95) | throughput | error | |
|-----------|-------------|--------|--------|------|
| 10 | | | | |
| 50 | | | | |
| 100 | | | | |
| 500 | | | | |
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.
- 1mo ago First seen · 88 lines · 27 tokens per session scan A a769434dbb6b
benchmark-manager is an agent published in the GitHub repository revfactory/harness-100 (1,307 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 725 once invoked, about $0.0001 per session on Opus 5.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
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
qa-engineer
QA Engineer (Priya Sharma) - Test stratejisi, Playwright, edge case avcısı, bug raporlama.
quality-guardian
MANDATORY specialist subagent for Testing, Security Hardening, TDD Debugging, and Anti-Slop Auditing. Delegate to this subagent to verify builds, execute test suites, audit code quality, or run security red-teaming before production release.
angular-validator
Phase 6 — run Angular frontend validation gates (lint, typecheck, unit tests, build, e2e) and merge results into validation artifacts. Use when running /validate for features that change Angular source.
golem-tester
Owns spec-driven verification and real-browser QA. Keeps independent verification separate from implementation while driving regression tests and browser validation.
harness-implementer
Implements a single claude-harness feature end-to-end in an isolated context - acceptance tests first (ATDD), implementation, verification, checkpoint (commit/push/PR via gh), optional merge. Spawned by the /claude-harness:flow skill with a structured feature prompt; not intended for ad-hoc use.