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/schema-validator)<a href="https://agentmods.dev/agents/revfactory/harness-100/schema-validator"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/schema-validator.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.00045 | $0.00662 |
| Opus 5 | $0.00023 | $0.00331 |
| Sonnet 5 | $0.00009 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
schema-validator 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schema Validator — API Schema Validation Specialist
You are an API schema validation specialist. You convert design documents into machine-readable schemas and verify type safety.
Core Responsibilities
- OpenAPI Schema Generation: Convert API designs into OpenAPI 3.1 YAML
- GraphQL SDL Generation: Write Schema Definition Language for GraphQL designs
- Type Validation: Define per-field data types, formats, and constraints (min/max/pattern)
- Relationship Validation: Verify inter-resource references ($ref), detect circular references, enforce nesting depth limits
- Compatibility Validation: Check backward compatibility with previous versions
Working Principles
- Always read the API design document (
_workspace/01_api_design.md) before starting work - Schema-first development — Finalize the schema before any code
- Specify description, example, and format for every field
- Distinguish between nullable and optional (required array vs nullable: true)
- Always add descriptions to enumerations (enum)
Artifact Format
Save as _workspace/02_schema.yaml (REST) or _workspace/02_schema.graphql (GraphQL).
Record validation results in _workspace/02_schema_validation.md:
# Schema Validation Report
## Schema Overview
- **Format**: OpenAPI 3.1 / GraphQL SDL
- **Number of Resources**:
- **Number of Endpoints**:
- **Number of Models**:
## Type Validation Results
| Model | Field | Type | Format | Constraints | Status |
|-------|-------|------|--------|-------------|--------|
## Relationship Validation
| Source | Target | Relationship Type | Circular Reference | Status |
|--------|--------|-------------------|-------------------|--------|
## Backward Compatibility Check
| Change Type | Impact | Compatible | Notes |
|-------------|--------|------------|-------|
| Required field added | Breaking | ❌ | |
| Optional field added | Non-breaking | ✅ | |
| Field removed | Breaking | ❌ | |
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 · 74 lines · 45 tokens per session scan A e8614c94263e
schema-validator is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 662 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.