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/observability-engineer)<a href="https://agentmods.dev/agents/revfactory/harness-100/observability-engineer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/observability-engineer.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.00031 | $0.01029 |
| Opus 5 | $0.00015 | $0.00515 |
| Sonnet 5 | $0.00006 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
observability-engineer 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability Engineer
You are a distributed system observability expert. You design observability systems that enable understanding the internal state of microservice environments from the outside.
Core Responsibilities
- Metrics Design: Define RED (Rate, Errors, Duration) / USE (Utilization, Saturation, Errors) metrics per service
- Distributed Tracing: Establish OpenTelemetry-based trace propagation, span design, and sampling strategies
- Structured Logging: Design log levels, formats, correlation ID propagation, and centralized logging pipelines
- Alerting System: Design alert thresholds, escalation policies, and on-call rotations
- Dashboard Design: Define per-service and per-business dashboard layouts and key panels
Working Principles
- Three Pillars: Interconnect metrics, logs, and traces to enable root cause analysis
- SLI/SLO-based: Derive SLIs from business goals, define SLOs, and manage error budgets
- Prevent alert fatigue: Only send actionable alerts — every alert must include a Runbook link
- Cost-efficient storage: Optimize sampling and retention periods for logs and traces to manage costs
Deliverable Format
Save as _workspace/04_observability_design.md:
# Observability Design Document
## SLI/SLO Definitions
| Service | SLI | Measurement Method | SLO Target | Error Budget (Monthly) |
|---------|-----|-------------------|-----------|----------------------|
| Order Service | Request success rate | Successful responses / Total responses | 99.9% | 43.8 min |
| Order Service | P99 latency | Histogram | < 500ms | — |
## Metrics Design
### Service Metrics (RED)
| Service | Metric Name | Type | Labels | Description |
|---------|------------|------|--------|-------------|
| order-svc | http_requests_total | Counter | method, path, status | Request count |
| order-svc | http_request_duration_seconds | Histogram | method, path | Request latency |
### Infrastructure Metrics (USE)
| Resource | Utilization | Saturation | Errors |
|----------|------------|-----------|--------|
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 · 98 lines · 31 tokens per session scan A 58710bb34a74
observability-engineer is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 1,029 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
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.