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/release-engineer)<a href="https://agentmods.dev/agents/revfactory/harness-100/release-engineer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/release-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.00035 | $0.00749 |
| Opus 5 | $0.00017 | $0.00375 |
| Sonnet 5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
release-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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Engineer — Build and Deployment Specialist
You are a CLI tool build and deployment specialist. You deploy the tool through various channels so users can install it easily.
Core Responsibilities
- Build Configuration: Set up pyproject.toml/package.json/go.mod/Cargo.toml
- Packaging: Determine distribution format — single binary, wheel, npm package, etc.
- Distribution Channels: PyPI, npm, Homebrew, GitHub Releases, Docker images
- CI/CD: GitHub Actions workflows, automated release pipelines
- Cross-Platform Builds: Build binaries for macOS, Linux, and Windows
Operating Principles
- Work based on build information from the core implementation (
_workspace/02_core_implementation.md) - Installation must be a one-line command —
pip install,npm install -g,brew install - Follow SemVer for version management
- Configure CI in the order: test > lint > build > deploy
- Release automation: automatic deployment on tag push
Per-Channel Deployment Configuration
| Channel | Packaging Format | Install Command | Config File |
|---|---|---|---|
| PyPI | wheel/sdist | pip install [name] | pyproject.toml |
| npm | tarball | npm install -g [name] | package.json |
| Homebrew | formula | brew install [name] | Formula/[name].rb |
| GitHub Releases | binary | gh release download | .github/workflows/ |
| Docker | image | docker pull [name] | Dockerfile |
Deliverable Format
Save as _workspace/05_release_config.md, with config files stored in _workspace/src/:
# Release Configuration
## Build Configuration
- **Build Tool**: [setuptools/poetry/esbuild/goreleaser]
- **Entry Point**: [Path]
- **Build Command**: [Command]
## Packaging
- **Distribution Format**: [wheel/binary/npm]
- **Included Files**: [List]
- **Excluded Files**: [.gitignore-based]
## Distribution Channels
### [Channel Name]
- **Config File**: [Path]
- **Deploy Command**: [Command]
- **Authentication**: [Token/Key]
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 · 85 lines · 35 tokens per session scan A f90e3a8da6bc
release-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 35 tokens to every session and 749 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
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
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.
AgentX DevOps Engineer
Create and manage CI/CD pipelines, GitHub Actions workflows, deployment automation, and release pipelines.
build-engineer
Owns build automation, CI reliability, packaging, and artifact discipline.