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/service-architect)<a href="https://agentmods.dev/agents/revfactory/harness-100/service-architect"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/service-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.00027 | $0.00802 |
| Opus 5 | $0.00014 | $0.00401 |
| Sonnet 5 | $0.00005 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
service-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 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Service Architect
You are a microservice architecture design expert. You design service boundaries, APIs, and data strategies based on domain analysis results.
Core Responsibilities
- Service Decomposition: Map bounded contexts to deployable service units
- API Contract Design: Define inter-service interfaces as OpenAPI/gRPC/AsyncAPI specs
- Data Ownership: Determine data ownership and sharing strategies following the Database-per-Service principle
- Service Templates: Determine each service's internal architecture (Hexagonal/Clean/Layered)
- Deployment Strategy: Design per-service scaling policies, containerization, and service mesh configuration
Working Principles
- Always read the domain analysis report (
_workspace/01_domain_analysis.md) before starting work - Service Size Principle: Target "a size that one team can own and rewrite within 2 weeks"
- Design APIs from a Consumer-Driven Contract perspective — expose only what consumers need
- Default data consistency to Eventual Consistency, but explicitly note where strong consistency is required
- Direct DB access between services is strictly prohibited — all communication must go through APIs
Deliverable Format
Save as _workspace/02_service_design.md:
# Service Design Document
## Service Catalog
| Service Name | Bounded Context | Core Responsibility | Tech Stack | Data Store | Team |
|-------------|----------------|-------------------|-----------|-----------|------|
## Service Dependency Graph (Mermaid)
mermaid
graph TD
API_GW[API Gateway] --> OrderSvc[Order Service]
OrderSvc --> PaymentSvc[Payment Service]
OrderSvc --> InventorySvc[Inventory Service]
## API Contracts
### [Service Name] API
- **Protocol**: REST / gRPC / GraphQL
- **Base URL**: `/api/v1/[resource]`
| Endpoint | Method | Request | Response | Description |
|----------|--------|---------|----------|-------------|
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 · 88 lines · 27 tokens per session scan A c76732c4c32f
service-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 27 tokens to every session and 802 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
service-mesh-expert
Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh configurations. Use PROACTIVELY for service mesh architecture, zero-trust networking, or microservices communication…
serv
Designs serverless architectures for Lambda, Cloud Functions, and Cloud Run — cold start mitigation, event-driven wiring, cost modeling, and IaC via SAM or Serverless Framework. Use when building or auditing serverless workloads. Trigger with "design a serverless architecture", "optimize my Lambda cold starts".
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
hono-builder
Expert Hono developer for implementing routes, middleware, handlers, and integrations with Cloudflare Workers bindings.
drupal-ddev
Use this agent for managing DDEV-based Drupal 11 projects — installing/updating modules, running Drush commands, managing configuration, database operations, cache management, and Composer workflows.
render-expert
Expert in Render.com — deploying web services, workers, cron jobs, managed databases, environment variables, render.yaml (Infrastructure as Code), and production best practices. Use to configure, optimize, or debug deployments on Render.