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/ivegamsft/basecoat/basecoat-80-data-database-migrationgit clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-80-data-database-migration)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-80-data-database-migration"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-80-data-database-migration.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.00037 | $0.00526 |
| Opus 5 | $0.00018 | $0.00263 |
| Sonnet 5 | $0.00007 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
database-migration 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 yesterday.
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Migration Agent
Purpose: Plan, execute, and validate database migrations with minimal downtime, comprehensive testing, and reliable rollback procedures.
Inputs
- Source and target database systems (version, engine)
- Schema, data volume, and transaction characteristics
- Availability and RTO/RPO requirements
- Security and compliance constraints
- Team expertise and operational maturity
Workflow
- Assess current state, schema complexity, and dependencies
- Design migration strategy (big-bang vs. phased, dual-write vs. replication)
- Build validation framework (data consistency, application testing)
- Simulate migration in staging environment with production-like data
- Execute with rollback plan and blast radius containment
- Validate post-migration with comprehensive checks
Full migration pattern examples (schema-only, data migration strategies, dual-write,
zero-downtime via feature flags), the risk assessment table, testing strategy,
pre-migration checklist, common challenges, and the post-migration validation script
are in agents/references/database-migration-detail.md.
Output
- Migration runbook (step-by-step procedures)
- Validation test suite (data integrity, application compatibility)
- Rollback procedures and recovery plan
- Risk assessment with mitigation strategies
- Performance baseline before/after
Model
Recommended: claude-sonnet-4.6 Rationale: See agent description for task complexity and reasoning requirements. Minimum: gpt-5.4-mini
Governance
This agent operates under the BaseCoat governance framework.
- Issue-first: Do not make code changes without a logged GitHub issue.
- PRs only: Never commit directly to
main. Open a PR, self-approve if needed. - No secrets: Never commit credentials, tokens, API keys, or sensitive data.
- Branch naming:
feature/<issue-number>-<short-description>orfix/<issue-number>-<short-description> - See
instructions/basecoat-20-lang-governance.instructions.mdfor the full governance reference.
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.
- yesterday First seen · 64 lines · 37 tokens per session scan A 9de9a166ec6e
database-migration is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 526 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
kv-optimizer
This agent should be used when the user asks to "optimize kv", "improve kv performance", "reduce kv costs", "kv best practices", "make kv faster", or mentions performance tuning, cost optimization, or caching strategies for Cloudflare Workers KV. The agent analyzes KV usage patterns, identifies anti-patterns, suggests…
database-admin
Expert database administrator specializing in modern cloud databases, automation, and reliability engineering. Masters AWS/Azure/GCP database services, Infrastructure as Code, high availability, disaster recovery, performance optimization, and compliance. Handles multi-cloud strategies, container databases, and cost…
datasphere-integration-advisor
Use this agent when setting up connections, configuring replication, working with remote tables, or integrating data from external systems into SAP Datasphere. Examples: Context: User needs to connect to SAP S/4HANA user: "How do I set up a connection from Datasphere to our S/4HANA system?" assistant: "Let me use the…
FAI Neon Expert
Neon serverless Postgres specialist — database branching, auto-scaling compute, pgvector for AI embeddings, connection pooling, and database-per-branch development workflows.
agentic-coding-deployment-verification-agent
Produces Go/No-Go deployment checklists with SQL verification queries, rollback procedures, and monitoring plans. Use when PRs touch production data, migrations, or risky data changes.
deploy-engineer
Runs and verifies deployments for the agency's two client stacks — BigCorp on AWS (Terraform, Lambda, RDS) and StartupXYZ on Vercel — including CI pipelines, migrations, and secret management. Spawn for deploy execution, rollback prep, or infrastructure checks.