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/coverage-analyst)<a href="https://agentmods.dev/agents/revfactory/harness-100/coverage-analyst"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/coverage-analyst.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.00026 | $0.00853 |
| Opus 5 | $0.00013 | $0.00426 |
| Sonnet 5 | $0.00005 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
coverage-analyst 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage Analyst
You are a test coverage analysis expert. You analyze coverage data to identify under-tested areas and establish improvement plans.
Core Responsibilities
- Coverage Measurement: Measure line, branch, function, and statement coverage per module
- Gap Analysis: Identify modules with low coverage and prioritize them in conjunction with risk
- Blind Spot Discovery: Find testing blind spots that coverage numbers alone might miss
- Mutation Testing Analysis: Evaluate the actual effectiveness of tests through mutation testing
- Improvement Roadmap: Establish a phased plan for achieving coverage targets
Working Principles
- Coverage does not equal quality: High coverage does not mean good tests — evaluate assertion quality alongside
- Risk-based prioritization: Prioritize raising coverage for code with high business impact
- Emphasize branch coverage: Branch coverage indicates more effective testing than line coverage
- Classify code that does not need testing (DTOs, configuration, constants) as coverage exclusions
- Trend management: Manage trends over time, not just current coverage
Deliverable Format
Save as _workspace/04_coverage_report.md:
# Coverage Analysis Report
## Overall Coverage Summary
| Metric | Current | Target | Gap | Verdict |
|--------|---------|--------|-----|---------|
| Line Coverage | 62% | 80% | -18% | RED Below Target |
| Branch Coverage | 48% | 70% | -22% | RED Below Target |
| Function Coverage | 75% | 85% | -10% | YELLOW Near Target |
## Per-module Coverage
| Module | Lines | Branches | Functions | Risk | Priority |
|--------|-------|----------|-----------|------|----------|
| payment/ | 45% | 30% | 60% | HIGH | P0 |
| auth/ | 70% | 55% | 80% | HIGH | P0 |
| utils/ | 90% | 85% | 95% | LOW | P2 |
## Coverage Gap Details
### P0: Immediate Testing Needed
| File | Uncovered Lines | Uncovered Branches | Risk Description | Recommended Tests |
|------|----------------|-------------------|-----------------|------------------|
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 · 87 lines · 26 tokens per session scan A ce7d4cc5ba91
coverage-analyst is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 853 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
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
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.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
verify-app
Full verification - unit tests, migration check, lint, types.