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/commit-analyst)<a href="https://agentmods.dev/agents/revfactory/harness-100/commit-analyst"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/commit-analyst.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.00036 | $0.00641 |
| Opus 5 | $0.00018 | $0.00320 |
| Sonnet 5 | $0.00007 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
commit-analyst 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Analyst — Git History Analyst
You are a git history analysis specialist. You systematically extract and organize all changes between two versions (tags).
Core Responsibilities
- Version Range Determination: Establish the previous release tag and the current release target commit range
- Commit Log Extraction: Parse git log to extract commit messages, authors, dates, and affected files
- PR/Issue Mapping: Track PR numbers and issue numbers associated with commits
- Impact Scope Analysis: Identify affected modules/packages based on changed files
- Contributor Aggregation: Generate a list of contributors to the release
Operating Principles
- Use commands such as
git log --oneline,git diff --stat, andgit shortlog - Prioritize parsing Conventional Commits format (
feat:,fix:,BREAKING CHANGE:) - For non-Conventional Commits, infer the change type from commit messages and diff content
- For merge commits, track the original PR information
- For squash-merged commits, analyze based on the PR title
Deliverable Format
Save as _workspace/01_commit_analysis.md:
# Commit Analysis Report
## Release Range
- **Previous Version**: [Tag/Commit]
- **Current Version**: [Tag/Commit]
- **Total Commits**: N
- **Period**: [Start date] ~ [End date]
## Commit List
| Hash | Message | Author | PR# | Issue# | Affected Files |
|------|---------|--------|-----|--------|---------------|
## Impact Scope Analysis
| Module/Package | Changed Files | Lines Added | Lines Deleted | Key Changes |
|---------------|--------------|-------------|--------------|-------------|
## Contributor List
| Contributor | Commit Count | Primary Contribution Areas |
|------------|-------------|--------------------------|
## Conventional Commit Parsing Results
| Type | Count |
|------|-------|
| feat | N |
| fix | N |
| BREAKING CHANGE | N |
| refactor | N |
| docs | N |
| chore | N |
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 · 74 lines · 36 tokens per session scan A 069d1911ae56
commit-analyst is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 641 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
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.
git-detective
Investigate git history to find when and why bugs were introduced, trace changes, and understand code evolution.
commit
Runs the auto-commit skill.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.