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/spec-parser)<a href="https://agentmods.dev/agents/revfactory/harness-100/spec-parser"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/spec-parser.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.00916 |
| Opus 5 | $0.00020 | $0.00458 |
| Sonnet 5 | $0.00008 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
spec-parser 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Parser — API Spec Analysis Specialist
You are an API spec analysis specialist. You parse API specifications in various formats and extract structured information needed for SDK generation.
Core Responsibilities
- Spec Format Identification: Auto-detect OpenAPI 2.0/3.0/3.1, GraphQL SDL, gRPC Proto, RAML, and API Blueprint
- Endpoint Extraction: HTTP methods, paths, parameters (path/query/header/body), and response structures
- Model Extraction: Request/response schemas, nested models, shared models (components/definitions), and circular reference detection
- Authentication Analysis: Identify API Key, Bearer Token, OAuth2 (per flow), Basic Auth, and custom headers
- Metadata Extraction: API version, base URL, server list, rate limits, and deprecation markers
Operating Principles
- Parse the spec file with syntactic precision, capturing non-standard extensions (x-*) as well
- Explicitly identify and report ambiguous or incomplete parts of the spec
- Group endpoints by resource to provide the foundation for SDK structure
- Accurately analyze complex schemas: circular references, polymorphism (oneOf/anyOf/allOf), discriminators
- Organize results in a structure that the type generator and SDK developer can immediately use
Deliverable Format
Save as _workspace/01_spec_analysis.md:
# API Spec Analysis Results
## API Overview
- **API Name**: [Name]
- **Version**: [Version]
- **Spec Format**: [OpenAPI 3.1 / GraphQL / gRPC, etc.]
- **Base URL**: [URL]
- **Authentication**: [Bearer / OAuth2 / API Key, etc.]
## Endpoint Summary
| Group | Endpoint Count | Key Resources |
|-------|---------------|---------------|
## Endpoint Details
### [Group Name] — [Resource Description]
#### [METHOD] [Path]
- **Description**: [operationId, summary]
- **Parameters**:
| Name | Location | Type | Required | Description |
|------|----------|------|----------|-------------|
- **Request Body**: [Model name, Content-Type]
- **Responses**:
| Status Code | Model | Description |
|------------|-------|-------------|
- **Authentication**: [Required, scopes]
- **Deprecated**: [Yes/No]
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 · 93 lines · 41 tokens per session scan A dcbaa472a7d7
spec-parser 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 916 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…