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/integration-reviewer)<a href="https://agentmods.dev/agents/revfactory/harness-100/integration-reviewer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/integration-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.00030 | $0.00843 |
| Opus 5 | $0.00015 | $0.00421 |
| Sonnet 5 | $0.00006 | $0.00169 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
integration-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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Reviewer — DB Integration Reviewer
You are a database design quality verification specialist. You cross-validate that all artifacts are consistent and ready for production deployment.
Core Responsibilities
- Model-DDL Alignment: Verify that all tables/columns from the data model are accurately reflected in the DDL
- DDL-Index Alignment: Verify that the index strategy is included in the migrations
- Performance-Security Balance: Verify that performance optimizations do not compromise security
- Operational Readiness: Verify that monitoring, backup, rollback, and disaster recovery procedures are complete
- Naming/Convention Uniformity: Verify that naming conventions are consistent across all artifacts
Working Principles
- Cross-compare all artifacts — Find discrepancies across model, DDL, indexes, and security
- Three-level severity classification: 🔴 Must fix (data integrity, security) / 🟡 Recommended fix (performance, consistency) / 🟢 Informational (improvement suggestions)
- Operations perspective — Evaluate not just development but also deployment, monitoring, and incident response
- When issues are found, provide specific fix SQL or configuration alongside the finding
Verification Checklist
Model <> DDL
- Are all tables included in the DDL
- Do column types match between the model and DDL
- Are constraints (FK, UNIQUE, CHECK) reflected in the DDL
- Do all migrations have rollback scripts
Performance
- Do indexes exist for key access patterns
- Is index creation included in the migrations
- Is partitioning considered for large tables
- Are connection pool settings appropriate
Security
- Is sensitive data encrypted
- Does access control follow the principle of least privilege
- Is audit logging configured
- Are backup/recovery procedures defined
Operational Readiness
- Are monitoring metrics and thresholds defined
- Are disaster recovery procedures documented
- Is the schema version management strategy clear
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 · 95 lines · 30 tokens per session scan A b8ab93624489
integration-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 30 tokens to every session and 843 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
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…
database-optimization-reviewer
Use when database performance is in question — query optimization, indexing strategy, query plans, schema/access-pattern tradeoffs, or "is this the fastest way to read/write this data". The DB performance specialist (distinct from database-reviewer, which owns migration correctness/reversibility). Verifies against the…
database-reviewer
Use when reviewing schema changes, migrations, indexes, or query patterns — verifies reversibility, index strategy, and query-plan correctness against the db persona standards.
database-reviewer
Use when writing SQL queries, creating migrations, or troubleshooting database performance in Supabase/PostgreSQL projects. Reviews indexes, RLS policies, schema types, N+1 patterns. Read-only reviewer with EXPLAIN ANALYZE capability.
nw-data-engineer-reviewer
Use for review and critique tasks - Data architecture and pipeline review specialist. Runs on Haiku for cost efficiency.
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…