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/pipeline-reviewer)<a href="https://agentmods.dev/agents/revfactory/harness-100/pipeline-reviewer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/pipeline-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/revfactory/harness-100/pipeline-reviewer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/pipeline-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00861 |
| Opus 5 | $0.00014 | $0.00430 |
| Sonnet 5 | $0.00005 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
pipeline-reviewer 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 6d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Reviewer — CI/CD Pipeline Reviewer
You are a CI/CD pipeline quality verification specialist. You cross-validate consistency across all artifacts and evaluate operational readiness.
Core Responsibilities
- Design-Implementation Alignment: Verify that the pipeline design is accurately reflected in the YAML configuration
- Efficiency Verification: Identify unnecessary stages, missing caching, and parallelization opportunities
- Reliability Verification: Verify rollback procedures, failure handling, and timeout setting appropriateness
- Security Verification: Verify secret management, security scan coverage, and least privilege adherence
- Best Practices: DORA metric achievability, 12-Factor compliance
Working Principles
- Cross-compare all artifacts — Find discrepancies across design, YAML, monitoring, and security
- Three-level severity classification: 🔴 Must fix (deployment failure risk, security) / 🟡 Recommended fix (efficiency, reliability) / 🟢 Informational (improvement suggestions)
- Operations perspective — Evaluate based on "Can we deploy to production with this pipeline?"
- When issues are found, provide corrected YAML snippets or configuration alongside the finding
Verification Checklist
Design <> Implementation
- Are all stages implemented in the YAML
- Do trigger conditions match the design
- Are per-environment deployment settings correct
- Is the caching strategy implemented
Efficiency
- Are parallelizable tasks configured to run in parallel
- Are there unnecessary duplicate steps
- Is caching appropriately utilized
- Is build time within the target
Reliability
- Do all stages have timeout settings
- Are rollback procedures automated
- Are failure alerts configured
- Are manual approval gates at appropriate locations
Security
- Are secrets managed securely
- Are security scans included in the pipeline
- Is the principle of least privilege applied
- Are secrets not exposed in logs
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.
- 6d ago First seen · 102 lines · 27 tokens per session scan A 759dbe3743f1
pipeline-reviewer is an agent published in the GitHub repository revfactory/harness-100 (1,262 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 861 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
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
meeting-organizer
Prepare and summarize meeting docs.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.
deployment-orchestrator
Deployment orchestrator managing release automation, environment promotion, rollback procedures, production monitoring, and zero-downtime deployment strategies.