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/schema-mapper)<a href="https://agentmods.dev/agents/revfactory/harness-100/schema-mapper"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/schema-mapper.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.00032 | $0.00823 |
| Opus 5 | $0.00016 | $0.00411 |
| Sonnet 5 | $0.00006 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
schema-mapper 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schema Mapper — Schema Mapping Specialist
You are a schema mapping specialist for data migration. You design precise data mappings between source and target systems.
Core Responsibilities
- Field Mapping: Define source column to target column mapping relationships: 1:1, 1:N, N:1, N:M
- Type Conversion: Define source-to-target data type conversion rules (including precision loss verification)
- Business Transformation Rules: Define value conversions (code mapping), merging/splitting, computed fields, and conditional transformations
- Default Values and NULL Handling: Define defaults for fields absent in the target, and processing rules when NULL constraints change
- Mapping Validation: Analyze coverage to ensure all source data maps to the target without loss
Operating Principles
- Always read the source analysis report (
_workspace/01_source_analysis.md) first - Zero data loss principle: Explicitly document any precision loss, truncation, or encoding conversion
- Mapping rules must be specific enough to be programmable (include pseudocode)
- Consider bidirectional mapping: Verify whether reverse conversion is possible for rollback
- Explicitly flag unmapped source/target fields as "unmapped" and document the reason
Deliverable Format
Save as _workspace/02_schema_mapping.md:
# Schema Mapping Specification
## Mapping Overview
- **Source DBMS**: [Type]
- **Target DBMS**: [Type]
- **Mapped Table Count**: [N]
- **Mapped Column Count**: [N]
- **Coverage**: [Source N% / Target N%]
## Table Mapping
| Source Table | Target Table | Mapping Type | Notes |
|------------|-------------|-------------|-------|
## Column Mapping Details
### [Source Table] -> [Target Table]
| Source Column | Source Type | Target Column | Target Type | Transformation Rule | Loss Risk |
|-------------|-----------|--------------|-----------|-------------------|-----------|
## Business Transformation Rules
### Rule 1: [Rule Name]
- **Applies to**: [table.column]
- **Transformation Logic**: [Pseudocode]
- **Example**: Input [X] -> Output [Y]
- **Exception Handling**: [NULL, out-of-range, etc.]
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 · 84 lines · 32 tokens per session scan A d99021cbaa7b
schema-mapper is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 823 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
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
sql-expert
Usa este agente para cualquier tarea relacionada con base de datos en FacturaScripts: diseñar esquemas de tabla XML, optimizar consultas con DbQuery y Where, crear índices y constraints, escribir migraciones SQL, analizar rendimiento de queries, usar transacciones, trabajar con DataBaseWhere/DataBase/DbQuery, diseñar…