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 dayfinggg/openai-codex-agent-skills --skill database-migration-rolloutgit clone --depth 1 https://github.com/dayfinggg/openai-codex-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/dayfinggg/openai-codex-agent-skills/database-migration-rollout)<a href="https://agentmods.dev/skills/dayfinggg/openai-codex-agent-skills/database-migration-rollout"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/database-migration-rollout/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/dayfinggg/openai-codex-agent-skills/database-migration-rollout"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/database-migration-rollout.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.00036 | $0.00393 |
| Opus 5.5 | $0.00014 | $0.00157 |
| Sonnet 5.5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
database-migration-rollout 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.
What it actually says
Make the migration compatible with the database and the application versions that coexist during rollout.
- Establish the engine and exact version, migration runner, current schema, data volume, indexes, replication, and deployment order. Inspect existing migration conventions before choosing a mechanism.
- Identify invariants, affected reads and writes, constraint violations, and dependent objects. Separate a structural change from data transformation and access-policy changes.
- Consult version-matched DDL documentation for lock level, table rewrite, transaction restrictions, and online or concurrent behavior. Do not infer safety from a fast empty-table test.
- Prefer an expand, compatible application change, bounded resumable backfill, and contract sequence when coexistence requires it. A simple atomic change does not need a speculative multistage rollout.
- Bound lock acquisition and retry according to actual traffic and operational constraints. Preserve data and stop on unexpected state. Do not cancel unrelated sessions or weaken constraints to make the migration finish.
- Validate on an authorized representative copy or fixture. Check values, constraints, query behavior, invalid indexes, migration-runner bookkeeping, and interrupted retry where relevant.
- Establish restoration before production execution. Distinguish transactional rollback, application rollback, compensating migration, and backup restoration. A down migration that drops newly written data is not lossless.
- Apply only within existing authorization and verify schema, data invariants, application compatibility, waits, and replication afterward.
Read the PostgreSQL migration procedure for PostgreSQL-specific DDL. Read PostgreSQL ALTER TABLE or the selected engine's official reference for its actual version.
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 · 19 lines · 36 tokens per session scan A 4d0f3f1b4649
database-migration-rollout is a skill published in the GitHub repository dayfinggg/openai-codex-agent-skills (8 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 393 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-10-30.
Other skills, from other repositories
neo4j-snowflake-graph-analytics-skill
Run Neo4j Graph Analytics algorithms (PageRank, Louvain, WCC, Dijkstra, KNN, Node2Vec, FastRP, GraphSAGE) directly inside Snowflake without moving data. Use when running graph algorithms against Snowflake tables via the Neo4j Snowflake Native App ("GDS Snowflake", "graph algorithms in Snowflake", "Neo4j Graph…
neo4j-agent-memory-skill
Authoritative reference for the neo4j-agent-memory Python package — a graph-native memory system for AI agents built on Neo4j — and for the hosted service (NAMS) at memory.neo4jlabs.com. Use this skill whenever the user mentions neo4j-agent-memory, agent memory with Neo4j, context graphs, the POLE+O model…
neo4j-aura-graph-analytics-skill
Serverless Aura Graph Analytics (AGA) GDS Sessions — covers GdsSessions, AuraGraphDataScience, AuraAPICredentials, DbmsConnectionInfo, SessionMemory, getorcreate, remote graph projection with gds.graph.project.cypher and gds.graph.project.remote, gds.graph.project.native, gds.graph.construct, graphdatascience client…
neo4j-document-import-skill
Ingests unstructured and semi-structured documents into Neo4j as a knowledge graph. Use when chunking PDFs, HTML, plain text, or Markdown; extracting entities and relationships from text with an LLM (SimpleKGPipeline, neo4j-graphrag); loading JSON via apoc.load.json; building Document→Chunk→Entity graph structures; or…
neo4j-gds-skill
Neo4j Graph Data Science (GDS) embedded plugin via Python client or Cypher — covers graphdatascience client 2.x, GraphDataScience, gds.graph.project.native, gds.graph.project.cypher, snakecase endpoints, graph catalog operations, stream/stats/mutate/write modes, memory estimation, PageRank, Louvain, WCC, FastRP, KNN…
neo4j-import-skill
Import structured data into Neo4j — LOAD CSV, CALL IN TRANSACTIONS, neo4j-admin database import full (offline bulk), apoc.load.csv/json, apoc.periodic.iterate, driver batch writes. Covers method selection, header file format, type coercion, null handling, ON ERROR modes, CONCURRENT TRANSACTIONS, pre-import constraint…