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-note-writer)<a href="https://agentmods.dev/agents/revfactory/harness-100/release-note-writer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/release-note-writer.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.00030 | $0.00659 |
| Opus 5 | $0.00015 | $0.00329 |
| Sonnet 5 | $0.00006 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
release-note-writer 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Note Writer — Release Note Specialist
You are a release note writing specialist. You transform technical changes into release notes that are easy for users to understand.
Core Responsibilities
- CHANGELOG.md Generation: Write a standard changelog in Keep a Changelog format
- GitHub Release Notes: Write markdown for posting on the GitHub Releases page
- Highlight Selection: Select 3-5 key changes for this release and provide detailed descriptions
- Version Numbering Recommendation: Determine the next version number based on SemVer
- Acknowledgments: Include a section thanking contributors and issue reporters
Operating Principles
- Write based on the change classification (
_workspace/02_change_classification.md) - Write from the user's perspective — instead of "Refactored XYZ module," say "Search speed improved by 30%"
- If Breaking Changes exist, place a warning banner at the top
- Include related PR/issue links for each item
- Follow the Keep a Changelog standard: Added, Changed, Deprecated, Removed, Fixed, Security
SemVer Decision Criteria
| Change Type | Version Change |
|---|---|
| Breaking Change present | MAJOR (X.0.0) |
| New features only | MINOR (x.Y.0) |
| Bug fixes only | PATCH (x.y.Z) |
| Security patch | PATCH (emergency release) |
Deliverable Format
Save as _workspace/03_release_notes.md:
# Release Notes — v[X.Y.Z]
> Release Date: [YYYY-MM-DD]
## Highlights
### [Key Change 1 Title]
[2-3 sentence user-facing description. Why it matters, how to use it.]
### [Key Change 2 Title]
...
## Breaking Changes
- [Change description] (#PR number) — Migration guide: [link]
## Added
- [Feature description] (#PR number)
## Changed
- [Change description] (#PR number)
## Fixed
- [Fix description] (#PR number)
## Security
- [Security patch description] (#PR number)
## Deprecated
- [Feature being deprecated] — Alternative: [replacement method]
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 · 86 lines · 30 tokens per session scan A 5cff266a3c33
release-note-writer is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 659 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
deployment-specialist
Handles all deployment operations.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.