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 skills add Jiangxianze/spring-agent-skills --skill flyway-safe-migrationgit clone --depth 1 https://github.com/Jiangxianze/spring-agent-skillsWrote 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/skills/jiangxianze/spring-agent-skills/flyway-safe-migration)<a href="https://agentmods.dev/skills/jiangxianze/spring-agent-skills/flyway-safe-migration"><img src="https://agentmods.dev/badge/skills/jiangxianze/spring-agent-skills/flyway-safe-migration/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/skills/jiangxianze/spring-agent-skills/flyway-safe-migration"><img src="https://agentmods.dev/badge/skills/jiangxianze/spring-agent-skills/flyway-safe-migration.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.00080 | $0.00681 |
| Opus 5 | $0.00040 | $0.00341 |
| Sonnet 5 | $0.00016 | $0.00136 |
| Haiku 4.5 | $0.00008 | $0.00068 |
Grade A, and why
flyway-safe-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 11d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flyway Safe Migration
Identify lock, rewrite, compatibility, transaction, rollback, and data-loss risks before a Flyway migration reaches production.
Collect context
Determine these inputs before assigning severity:
- database engine and exact major version;
- Flyway version and transaction configuration;
- table size, row count, write rate, and deployment traffic;
- application versions that may run during rolling deployment;
- statement timeout, lock timeout, replication, and maintenance-window constraints;
- available backup, restore, and roll-forward procedure.
If context is missing, state assumptions and give conditional findings. Never promise that DDL is online or lock-free from syntax alone.
Review workflow
- Read migrations in version order and identify schema state before and after the change.
- Classify every statement as metadata-only, validation scan, table scan, table rewrite or copy, blocking index build, data backfill, or destructive change for the target engine and version.
- Analyze lock acquisition and duration, including lock-queue amplification when a DDL statement waits behind another transaction.
- Check mixed-version compatibility. Apply expand-contract when old and new application versions overlap.
- Separate schema changes from large backfills when batching, throttling, observability, or restartability is required.
- Check Flyway transaction behavior. Flag statements that cannot run inside the migration transaction or that cause implicit commits.
- Define abort signals, verification queries, and a roll-forward path. Treat down migrations as optional evidence, not proof of safe rollback.
- Offer a safe rewrite with explicit engine and version scope.
Always inspect
DROP, truncate, narrowing type changes, and rename compatibility windows;NOT NULL, defaults, unique checks, foreign keys, and constraint validation scans;- non-concurrent or non-online index builds;
- full-table
UPDATEorDELETEstatements and transaction log growth; - MySQL metadata locks, implicit commits, and requested
ALGORITHMorLOCKbehavior; - PostgreSQL
CREATE INDEX CONCURRENTLY, invalid index cleanup, and transaction restrictions; - checksum edits to migrations already applied in shared environments;
- repeatable migrations whose side effects are not idempotent.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 63 lines · 80 tokens per session scan A 507d9f868871
flyway-safe-migration is a skill published in the GitHub repository Jiangxianze/spring-agent-skills (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 80 tokens to every session and 681 once invoked, about $0.0004 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-31.
Other skills, from other repositories
supabase-cli
This skill should be used when user asks to "use supabase CLI", "supabase init", "supabase start", "run migrations", "deploy edge functions", "manage Supabase project", or works with the supabase command-line tool for local development and project management.
supabase-js
This skill should be used when user asks to "use supabase-js", "query Supabase database", "supabase auth", "supabase storage", "supabase realtime", "supabase edge functions", or works with the @supabase/supabase-js JavaScript/TypeScript SDK.
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.
supabase-postgres-best-practices
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the…
ciel-ml-and-data-patterns
CIEL's framework for PyTorch ML patterns and Postgres data optimization.
database-migrations
Safe, zero-downtime database schema changes and data backfills.