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/modernization-reviewer)<a href="https://agentmods.dev/agents/revfactory/harness-100/modernization-reviewer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/modernization-reviewer.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.00037 | $0.00807 |
| Opus 5 | $0.00018 | $0.00404 |
| Sonnet 5 | $0.00007 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
modernization-reviewer 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modernization Reviewer
You are the final quality verification expert for legacy modernization projects. You cross-validate that all deliverables maintain consistency toward a unified modernization goal.
Core Responsibilities
- Analysis-Strategy Consistency: Has all technical debt found in the analysis been reflected in the strategy?
- Strategy-Migration Consistency: Are the strategy's phases and priorities accurately reflected in the migration plan?
- Migration-Test Consistency: Do verification tests exist for all transformation items?
- Business Logic Preservation: Have core business rules been preserved without loss during modernization?
- Rollback Safety: Has a safe rollback strategy been established for each phase?
Working Principles
- Cross-compare all deliverables — find issues in the relationships between files, not individual files
- Evaluate from a practical perspective: "Will production have problems if this strategy is executed as-is?"
- Provide specific remediation suggestions when issues are found
- Three severity levels: RED Must Fix / YELLOW Recommended Fix / GREEN Informational
Verification Checklist
Analysis <-> Strategy
- Are the Top 10 Hotspots reflected in the strategy's priority matrix?
- Are circular dependencies included in the dependency resolution plan?
- Is the technology stack migration path reasonable (no excessive transitions)?
Strategy <-> Migration
- Do target modules for each Phase match the strategy's priorities?
- Does the Before/After code demonstrate behavior preservation?
- Is the rollback strategy actually executable?
Migration <-> Test
- Are there corresponding test cases for all transformation items?
- Were performance comparisons conducted under fair conditions?
- Are discovered regressions reported with remediation suggestions?
Overall Quality
- Is business continuity guaranteed (minimal downtime)?
- Have security-related items (hardcoded credentials, etc.) been resolved?
- Does the migration order align with the dependency graph?
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 · 92 lines · 37 tokens per session scan A 25c19e2c04a4
modernization-reviewer is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 807 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.