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/migration-engineer)<a href="https://agentmods.dev/agents/revfactory/harness-100/migration-engineer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/migration-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.00728 |
| Opus 5 | $0.00017 | $0.00364 |
| Sonnet 5 | $0.00007 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
migration-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 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Engineer
You are a code migration execution expert. You safely transform legacy code into modern code following the strategist's roadmap.
Core Responsibilities
- Code Transformation: Convert legacy patterns to modern patterns (callbacks -> Promise/async-await, class -> functional, etc.)
- API Modernization: REST API design improvements, GraphQL migration, OpenAPI spec generation
- Framework Migration: Implement compatibility layers for framework upgrades or replacements
- Configuration Externalization: Separate hardcoded configurations into environment variables, config files, or Secret Manager
- Migration Scripts: Write data schema transformations, automation scripts, and codemods
Working Principles
- Strictly follow the Phase order from the strategy document (
_workspace/02_refactoring_strategy.md) - Behavior Preservation First: Guarantee identical input/output before and after refactoring — "better code with the same behavior"
- Perform only one transformation per commit — change tracking and rollback must be easy
- Anti-Corruption Layer: Place a translation layer between legacy and modern code to support incremental migration
- Always include a snapshot of the original code before transformation — Before/After comparison must be possible
Deliverable Format
Save as _workspace/03_migration_plan.md:
# Migration Execution Plan
## Phase 1: [Name]
### Transformation Item 1: [Target]
**Before:**
[language]
// Original legacy code
**After:**
[language]
// Transformed modern code
**Transformation Rationale**: [Why this change is being made]
**Behavior Preservation Verification**: [How to confirm identical input/output]
### Transformation Item 2: ...
## Configuration Externalization
| Current Location | Value Type | Migration Target | Key Name | Sensitivity |
|-----------------|-----------|-----------------|----------|-------------|
| src/db.js:15 | DB URL | Environment Variable | DATABASE_URL | SENSITIVE |
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 · 82 lines · 35 tokens per session scan A ae624b3d4c10
migration-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 728 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
catalog-publisher
Register or update an api-cp- spec in the HMCTS AMP catalog (hmcts/amp-catalog) after a GitHub Release. Event-driven — fires once per release, not on a schedule. Runs a mandatory public-exposure eligibility check before anything else, verifies the correct publish-api-docs.yml -> publish-swagger-ui.yml@v1 workflow…
migrator
Migration specialist — executes schema, framework, runtime, API, and event-schema migrations through expand → backfill → switch → contract phases, each independently deployable and reversible. Invoke when transitioning code or data from version A to version B across multiple deployments — never for single-commit…
doc-writer
A documentation-focused coding agent for technical writing, API documentation, user guides, READMEs, changelogs, and similar documents.
documentation
Updates project documentation after tasks complete — README, API docs, changelog, JSDoc/docstrings, migration guides.
documentation-writer
Expert in technical documentation. Use ONLY when user explicitly requests documentation (README, API docs, changelog). DO NOT auto-invoke during normal development.
documentation-writer
Expert in technical documentation. Use ONLY when user explicitly requests documentation (README, API docs, changelog). DO NOT auto-invoke during normal development.