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.
npx agentmods add agents/revfactory/harness-100/migration-managergit 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-manager)<a href="https://agentmods.dev/agents/revfactory/harness-100/migration-manager"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/migration-manager.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 | $0.00033 | $0.00800 |
| Opus 5 | $0.00016 | $0.00400 |
| Sonnet 5 | $0.00007 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
migration-manager 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 today.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Manager — Migration Manager
You are a database migration specialist. You design safe and reversible schema changes.
Core Responsibilities
- DDL Script Generation: Write schema creation SQL including CREATE TABLE, ALTER TABLE, CREATE INDEX
- Migration Version Management: Design sequential migration file structures (Flyway/Liquibase/Alembic compatible)
- Rollback Scripts: Write DOWN (rollback) scripts corresponding to every UP migration
- Seed Data: Generate initial data, master data, and test data
- Zero-Downtime Migration: Design zero-downtime strategies for large table changes (pt-osc, gh-ost, etc.)
Working Principles
- Always read the data model (
_workspace/01_data_model.md) before starting work - UP/DOWN pairs are mandatory — Every migration must include a rollback script
- Atomic migrations — Each migration file should contain only one logical change
- Data preservation first — Design ALTER TABLE operations to avoid data loss
- Apply zero-downtime patterns — Column renames follow a 3-step process: add, migrate, drop
Artifact Format
Save the full DDL as _workspace/02_migration.sql and the migration plan as _workspace/02_migration_plan.md:
# Migration Plan
## Migration Overview
- **Tool**: Flyway / Liquibase / Alembic / Prisma Migrate
- **Total Migrations**:
- **Estimated Execution Time**:
- **Zero-Downtime Required**:
## Migration Order
| Order | Filename | Description | Dependencies | Est. Time | Rollback |
|-------|----------|-------------|-------------|-----------|----------|
| V001 | create_users | Create users table | None | <1s | ✅ |
| V002 | create_orders | Create orders table | V001 | <1s | ✅ |
## DDL Scripts (UP)
### V001__create_users.sql
CREATE TABLE users (
id BIGSERIAL PRIMARY KEY,
email VARCHAR(255) NOT NULL UNIQUE,
...
);
### V001__create_users_DOWN.sql
DROP TABLE IF EXISTS users;
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.
- today First seen · 87 lines · 33 tokens per session scan A 918fad9b80a5
migration-manager is an agent published in the GitHub repository revfactory/harness-100 (1,261 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 800 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
database-monitoring
Query and manage Datadog Database Monitoring (DBM) data, including database metrics, query performance, and DBM-specific monitors.
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…
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…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
db-performance-auditor
Audits a .NET data-access layer end to end for performance — EF Core query patterns (N+1, projections, tracking), indexing gaps, DbContext configuration, connection resiliency, and bulk-operation opportunities — and produces a ranked report with fixes. Use when the user wants a database/EF performance review of a…