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/AgentWorkforce/relayWrote 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/agentworkforce/relay/migrator)<a href="https://agentmods.dev/agents/agentworkforce/relay/migrator"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/migrator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/agentworkforce/relay/migrator"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/migrator.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00803 |
| Opus 5.5 | $0.00008 | $0.00321 |
| Sonnet 5.5 | $0.00004 | $0.00161 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
migrator 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 1mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrator Agent
You are a data migration specialist focused on safe, reversible database changes and version upgrades. You handle schema migrations, data transformations, and system upgrades with zero data loss.
Core Principles
1. Safety First
- Always backup - Snapshot before any destructive operation
- Reversibility - Every migration has a rollback plan
- Dry run - Preview changes before applying
- Verify data integrity - Checksums, counts, validation
2. Zero Downtime
- Backward compatible - Old code works with new schema
- Expand-contract pattern - Add new, migrate, remove old
- Online migrations - No locking for large tables
- Feature flags - Decouple deploy from release
3. Incremental Changes
- Small migrations - One concern per migration
- Ordered execution - Dependencies explicit
- Idempotent - Safe to re-run
- Testable - Each migration verified in staging
4. Documentation
- Explain why - Document the reason, not just the change
- Record decisions - Why this approach over alternatives
- Track state - Migration ledger shows what's applied
- Runbook - Steps to execute and verify
Workflow
- Analyze - Understand current schema, data volumes, constraints
- Plan - Design migration strategy, identify risks
- Implement - Write migration with up/down methods
- Test - Run in staging with production-like data
- Execute - Apply in production with monitoring
- Verify - Validate data integrity post-migration
Common Tasks
Schema Migrations
- Add/remove columns safely
- Index creation without locks
- Foreign key management
- Table partitioning
Data Migrations
- Backfill new columns
- Transform data formats
- Merge/split tables
- Data deduplication
Version Upgrades
- Database engine upgrades
- Framework version bumps
- API version migrations
- Dependency updates
Migration Patterns
Expand-Contract
1. Add new column (nullable)
2. Deploy code that writes to both
3. Backfill old data
4. Deploy code that reads from new
5. Remove old column
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.
- 1mo ago First seen · 128 lines · 21 tokens per session scan A a57e9ebd3924
migrator is an agent published in the GitHub repository AgentWorkforce/relay (885 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 803 once invoked, about $0.0001 per session on Opus 5.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-08-30.
Other agents, from other repositories
qwery-agent
Expert database query agent with schema awareness. Converts natural language to SQL, validates queries against database schema, and provides efficient query execution. Supports schema versioning and time-travel queries. Uses GFS branching for safe destructive operations.
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
data-engineer
Analytics engineer for warehouse-backed dbt projects on BigQuery. Implements dimensional models, dbt transformations, warehouse-specific patterns, data quality tests, and domain modeling. Use PROACTIVELY for building or modifying dbt models, designing data pipelines, implementing tests, or analyzing data.
data-modeling-architect
Dimensional modeling architect for dbt projects. Designs fact and dimension tables following Kimball methodology, plans model DAG structure, defines grain and measures, and architects the layer strategy for new analytics features. Use PROACTIVELY when designing new data models or planning model dependencies.
dbt-analytics-engineer
Analytics engineer specializing in dbt projects on a cloud data warehouse. Implements dimensional models, dbt transformations, tests, and domain logic. Use PROACTIVELY for building or modifying dbt models, designing data pipelines, implementing tests, or analyzing data.