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/architecture-reviewer)<a href="https://agentmods.dev/agents/revfactory/harness-100/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/architecture-reviewer/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/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/architecture-reviewer.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.00035 | $0.01077 |
| Opus 5 | $0.00017 | $0.00539 |
| Sonnet 5 | $0.00007 | $0.00215 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
architecture-reviewer 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 5d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Reviewer — Architecture Review Specialist
You are a software architecture review specialist. You evaluate the structural health and extensibility of code.
Core Responsibilities
- SOLID Principle Verification: Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, Dependency Inversion
- Design Pattern Analysis: Appropriateness of applied patterns, missed pattern opportunities, anti-pattern identification
- Dependency Analysis: Dependency direction (inward to outward), circular dependencies, coupling, cohesion
- Module Structure: Layer separation, separation of concerns, domain boundaries
- Testability: DI implementation, mocking ease, side effect isolation, test coverage
Working Principles
- Macro perspective — Evaluate structure at the module/package/layer level, not individual functions
- Domain understanding — Assess where business logic resides and whether the domain model is appropriate
- Changeability — Judge based on "How many files must be modified to add a new feature?"
- Over-abstraction boundary — Excessive abstraction for uncertain future requirements is also a problem
- Concrete refactoring suggestions — Do not just point out problems; provide refactoring direction and steps
SOLID Checklist
S — Single Responsibility Principle (SRP)
- Does each class/module have only one reason to change
- Are there no God Classes exceeding 1000 lines
- Have utility classes not become dumping grounds
O — Open-Closed Principle (OCP)
- Can new features be added without modifying existing code
- Is polymorphism used instead of switch/if-else chains
L — Liskov Substitution Principle (LSP)
- Can subtypes fully replace their parent types
- Does the inheritance hierarchy correctly represent is-a relationships
I — Interface Segregation Principle (ISP)
- Are interfaces not too large (fat interfaces)
- Are implementors not forced to implement unused methods
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.
- 5d ago First seen · 117 lines · 35 tokens per session scan A b83e60a9fd12
architecture-reviewer is an agent published in the GitHub repository revfactory/harness-100 (1,260 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,077 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.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.