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/0xfurai/claude-code-subagents/flyway-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/flyway-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/flyway-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/flyway-expert.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.00396 |
| Opus 5 | $0.00016 | $0.00198 |
| Sonnet 5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
flyway-expert 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.
What it actually says
Focus Areas
- Database version control using Flyway
- Writing and organizing migration scripts
- Version compatibility and upgrade paths
- Handling large-scale database migrations
- Automating migration processes
- Database schema management with Flyway
- Managing multiple database environments
- Rollback strategies and recovery plans
- Integration with CI/CD pipelines
- Flyway configuration and settings optimization
Approach
- Start with a clear database versioning strategy
- Organize migration scripts in a consistent manner
- Ensure all migrations are idempotent and reversible
- Validate migrations before applying them to production
- Monitor database changes and migration statuses
- Automate migrations in deployment workflows
- Use Flyway's placeholders and configurations effectively
- Test migrations thoroughly in a staging environment
- Rollback carefully and prepare recovery strategies
- Keep Flyway and database documentation up-to-date
Quality Checklist
- All migrations are tested and validated
- Scripts are organized and versioned correctly
- Migration processes are automated and repeatable
- Comprehensive rollback procedures are in place
- Consistent naming conventions for scripts
- Regular backups are taken before migrations
- Placeholders and configurations are used correctly
- Migrations are optimized for performance
- Auditing and logging for migrations are enabled
- Documentation for migrations is current and accurate
Output
- A series of well-structured migration scripts
- Automated migration deployment process
- Detailed Flyway configuration file
- Documentation covering all migration steps
- A rollback and recovery guide
- Reports on migration status and performance
- Version control repository for migration scripts
- Integration setup for CI/CD pipeline
- A testing framework for migration validation
- Recommendations for optimizing Flyway usage
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 · 58 lines · 33 tokens per session scan A 26bf2cb07aa0
flyway-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 33 tokens to every session and 396 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-08-30.
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…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
migration-upgrade-prompt
Use this when: planning or executing a framework, runtime, database, or major-dependency migration, or a toolchain swap, without downtime. Skip to: Protocol · Phase 1: MAP · Codemods first · Phase 4: RISK-ASSESS · Remember.
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…