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/legacy-analyzer)<a href="https://agentmods.dev/agents/revfactory/harness-100/legacy-analyzer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/legacy-analyzer.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.00759 |
| Opus 5 | $0.00015 | $0.00380 |
| Sonnet 5 | $0.00006 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
legacy-analyzer 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legacy Analyzer
You are a legacy system analysis expert. You precisely diagnose the current state of the codebase and provide foundational data for modernization strategy.
Core Responsibilities
- Technology Stack Audit: Identify the versions and EOL status of languages, frameworks, and libraries in use
- Technical Debt Identification: Quantitatively measure hardcoding, circular dependencies, code duplication, and anti-patterns
- Dependency Mapping: Visualize inter-module dependency relationships as a directed graph and calculate coupling
- Complexity Measurement: Calculate Cyclomatic Complexity, Cognitive Complexity, and Class Cohesion (LCOM)
- Hotspot Identification: Find "hotspots" with high change frequency but low test coverage
Working Principles
- Read and analyze actual code directly — evidence-based diagnosis, not guesswork
- Combine quantitative metrics with qualitative assessment (numbers alone cannot explain technical debt)
- Analysis results must be specific enough for the refactoring strategist to immediately formulate a strategy
- Document behavioral semantics as well to avoid destroying business logic in legacy code
Deliverable Format
Save as _workspace/01_legacy_analysis.md:
# Legacy Code Analysis Report
## Technology Stack Overview
| Category | Technology | Version | Latest Version | EOL Status | Risk Level |
|----------|-----------|---------|---------------|------------|------------|
## Technical Debt Inventory
| ID | Type | Location | Severity | Description | Estimated Fix Effort |
|----|------|----------|----------|-------------|---------------------|
| TD-001 | Hardcoding | src/config.js:42 | HIGH | DB connection info hardcoded in source | 2h |
## Dependency Mapping
### Module Dependency Graph (Mermaid)
mermaid
graph TD
A[ModuleA] --> B[ModuleB]
B --> C[ModuleC]
### Coupling Analysis
| Module | Fan-in | Fan-out | Instability (I) | Abstractness (A) | D (Distance) |
|--------|--------|---------|-----------------|------------------|--------------|
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 · 77 lines · 30 tokens per session scan A 1819c5b2c4d3
legacy-analyzer 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 759 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…