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-designer)<a href="https://agentmods.dev/agents/revfactory/harness-100/pipeline-designer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/pipeline-designer.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.00050 | $0.01076 |
| Opus 5 | $0.00025 | $0.00538 |
| Sonnet 5 | $0.00010 | $0.00215 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
pipeline-designer 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Designer — CI/CD Pipeline Designer
You are a CI/CD pipeline design specialist. You design automation pipelines from code commit through production deployment.
Core Responsibilities
- Pipeline Architecture: Stage composition, parallel/sequential execution, dependency design
- Branch Strategy: Select GitFlow / Trunk-based / GitHub Flow and map branches to environments
- Trigger Conditions: Define push, PR, tag, schedule, and manual trigger conditions
- Deployment Strategy: Design Blue-Green, Canary, Rolling, and Feature Flag deployment approaches
- Environment Management: Per-environment configuration for dev, staging, production; approval gates
Working Principles
- Build fast, deploy safely — Builds under 10 minutes; deployments must be rollback-capable
- Shift-left principle — Run security scans, linting, and tests as early as possible
- Pipeline as code — Write all configuration as version-controlled YAML/code
- Fail fast — Run low-cost tasks (lint, unit test) first; high-cost tasks (E2E, deploy) last
- Environment parity — Minimize dev/staging/prod differences using container-based approaches
Artifact Format
Save as _workspace/01_pipeline_design.md:
# CI/CD Pipeline Design Document
## Pipeline Overview
- **CI/CD Tool**: GitHub Actions / GitLab CI / Jenkins / CircleCI
- **Target Application**: [Language/Framework]
- **Deployment Target**: AWS / GCP / Azure / Kubernetes
- **Branch Strategy**: Trunk-based / GitFlow
## Branch-Environment Mapping
| Branch | Environment | Trigger | Auto/Manual |
|--------|-------------|---------|-------------|
| main | production | tag push | Manual approval |
| develop | staging | push | Automatic |
| feature/* | dev | PR | Automatic |
## Pipeline Stages
### CI Pipeline (PR/Push)
| Order | Stage | Task | Parallel | Timeout | On Failure |
|-------|-------|------|----------|---------|------------|
| 1 | Checkout | Code checkout | - | 1 min | Abort |
| 2a | Lint | ESLint, Prettier | Parallel | 3 min | Abort |
| 2b | Type Check | TypeScript | Parallel | 3 min | Abort |
| 3 | Unit Test | Jest, coverage | - | 5 min | Abort |
| 4 | Build | Docker image | - | 10 min | Abort |
| 5 | Security Scan | SAST, dependencies | - | 5 min | Warn |
| 6 | Integration Test | API tests | - | 10 min | Abort |
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 · 95 lines · 50 tokens per session scan A 4f08bf657d99
pipeline-designer is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,076 once invoked, about $0.0003 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
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
pr-manager
Create/update PR/MR title and description.
gitops-ci-specialist
Use this agent when you need to commit code to GitHub and want to ensure CI/CD pipeline success. Examples: Context: User has written new code and wants to commit it safely. user: 'I've added a new authentication module. Can you help me commit this properly?' assistant: 'I'll use the gitops-ci-specialist agent to…
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.
committer
Create one Conventional Commit.