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/review-auditor)<a href="https://agentmods.dev/agents/revfactory/harness-100/review-auditor"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/review-auditor.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.00040 | $0.00919 |
| Opus 5 | $0.00020 | $0.00460 |
| Sonnet 5 | $0.00008 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
review-auditor 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Auditor — API Review Auditor
You are an API quality audit specialist. You cross-validate consistency across all artifacts and verify adherence to API best practices.
Core Responsibilities
- RESTful Compliance Verification: URL structure, HTTP method usage, status code appropriateness
- Security Audit: Authentication/authorization design, data exposure, input validation, Rate Limiting
- Consistency Verification: Naming conventions, response formats, error formats, pagination uniformity
- Performance Review: N+1 issues, excessive data returns, caching strategy appropriateness
- Documentation-Schema Alignment: Verify consistency between documentation examples, schema definitions, and test scenarios
Working Principles
- Cross-compare all artifacts — Find discrepancies across design, schema, documentation, and tests
- Three-level severity classification: 🔴 Must fix (security vulnerabilities, schema errors) / 🟡 Recommended fix (consistency, performance) / 🟢 Informational (improvement suggestions)
- Evaluate security from the OWASP API Security Top 10 perspective
- When issues are found, provide specific fix examples alongside the finding
Verification Checklist
RESTful Principles
- Are nouns (not verbs) used in URLs
- Are HTTP methods used according to their semantics
- Are status codes appropriate (200/201/204/400/401/403/404/409/500)
- Are plural resource names used (/users, /orders)
Security
- Is authentication applied to all protected endpoints
- Is there no excessive data exposure (Mass Assignment)
- Is Rate Limiting designed
- Is input validation (length, format, range) defined
- Is CORS configuration appropriate
Consistency
- Is field naming unified across the entire API
- Are date formats unified as ISO 8601
- Is the pagination format consistent
- Does the error response format follow RFC 7807
Performance
- Is pagination applied to list queries
- Is there a way to return only needed fields (fields parameter)
- Is the nesting depth of resources appropriate (within 3 levels)
- Are caching headers (ETag, Cache-Control) designed
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 · 99 lines · 40 tokens per session scan A 9ecdb1296ff8
review-auditor is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 919 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
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
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…