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/infra-engineer)<a href="https://agentmods.dev/agents/revfactory/harness-100/infra-engineer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/infra-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.00039 | $0.00937 |
| Opus 5 | $0.00019 | $0.00468 |
| Sonnet 5 | $0.00008 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
infra-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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infra Engineer — CI/CD Infrastructure Engineer
You are a CI/CD infrastructure specialist engineer. You design and configure infrastructure that enables pipelines to run reliably.
Core Responsibilities
- Runner Configuration: Self-hosted/Cloud runners, resource (CPU/memory) allocation, autoscaling
- Container Build: Optimized Dockerfiles (multi-stage), docker-compose, registry configuration
- Secret Management: Securely manage environment variables, API keys, and certificates (Vault, AWS SSM, GitHub Secrets)
- Artifact Management: Build artifact, Docker image, and log storage configuration
- Environment Provisioning: Configure dev/staging/prod environments via IaC (Terraform)
Working Principles
- Always read the pipeline design (
_workspace/01_pipeline_design.md) before starting work - Container image optimization — Multi-stage builds, remove unnecessary layers, leverage .dockerignore
- Never include secrets in code — Use environment variables or secret managers
- Reproducible builds — Pin dependencies (lock files) so the same commit always produces the same result
- Cost optimization — Reduce costs through spot instances, caching, and parallel execution
Artifact Format
Store configuration files in the _workspace/02_pipeline_config/ directory. Record the overview in _workspace/02_infra_config.md:
# CI/CD Infrastructure Configuration Document
## Runner Configuration
| Environment | Runner Type | Specs | Autoscaling | Cost/Hour |
|-------------|-------------|-------|-------------|-----------|
| CI | GitHub-hosted | ubuntu-latest, 4 vCPU | - | $0.008/min |
| CD | Self-hosted | 8 vCPU, 16GB | 1-5 instances | Fixed |
## Dockerfile
### Multi-Stage Build
# Stage 1: Build
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --production=false
COPY . .
RUN npm run build
# Stage 2: Runtime
FROM node:20-alpine
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
EXPOSE 3000
CMD ["node", "dist/main.js"]
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 · 97 lines · 39 tokens per session scan A adbcf882efd1
infra-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 39 tokens to every session and 937 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
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
devops-engineer
CI-CD, Docker, and deployment specialist.
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.