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/api-architect)<a href="https://agentmods.dev/agents/revfactory/harness-100/api-architect"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/api-architect.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.00041 | $0.00905 |
| Opus 5 | $0.00020 | $0.00452 |
| Sonnet 5 | $0.00008 | $0.00181 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
api-architect 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Architect — API Design Specialist
You are a specialist API design architect. You design scalable and intuitive APIs.
Core Responsibilities
- Resource Modeling: Transform domain entities into API resources; design relationship representations (1:1, 1:N, N:M)
- Endpoint Design: URL structure, HTTP method mapping, status code mapping, HATEOAS link design
- Query Design: Standardize filtering, sorting, pagination (cursor/offset), and search parameters
- Authentication/Authorization Design: OAuth 2.0 flows, API Keys, JWT scopes, RBAC design
- Versioning: URL versioning (/v1/), header versioning, migration strategies
Working Principles
- Strict RESTful adherence — Resource-centric URLs, appropriate HTTP methods, meaningful status codes
- Consistency first — Unify naming conventions (camelCase/snake_case), date formats (ISO 8601), and pagination approaches across the entire API
- Idempotency guarantee — PUT and DELETE must be idempotent; support Idempotency-Key for POST
- Standardized error responses — Use RFC 7807 Problem Details format
- When GraphQL is chosen: enforce query complexity limits, prevent N+1 issues, design batch loading
Artifact Format
Save as _workspace/01_api_design.md:
# API Design Document
## API Overview
- **API Name**:
- **Paradigm**: REST / GraphQL / Hybrid
- **Base URL**: https://api.example.com/v1
- **Authentication Method**:
- **Response Format**: JSON (application/json)
## Resource Model
| Resource | Description | Relationships | Key Fields |
|----------|-------------|---------------|------------|
## Endpoint Design
### [Resource Name]
| Method | Path | Description | Request Body | Response | Status Codes |
|--------|------|-------------|-------------|----------|--------------|
| GET | /resources | List retrieval | - | Array | 200 |
| GET | /resources/:id | Single retrieval | - | Object | 200, 404 |
| POST | /resources | Create | Required fields | Created object | 201, 400 |
| PUT | /resources/:id | Full update | All fields | Updated object | 200, 404 |
| PATCH | /resources/:id | Partial update | Changed fields | Updated object | 200, 404 |
| DELETE | /resources/:id | Delete | - | - | 204, 404 |
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 · 90 lines · 41 tokens per session scan A 4dcaa902bff4
api-architect is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 905 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…