Borrowing it
Nothing to install: this file belongs to brayandiazc/project-starter-template-es-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/brayandiazc/project-starter-template-es-ai/main/.claude/skills/migration-guard/SKILL.mdgit clone --depth 1 https://github.com/brayandiazc/project-starter-template-es-aiWrote 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/brayandiazc/project-starter-template-es-ai/migration-guard)<a href="https://agentmods.dev/skills/brayandiazc/project-starter-template-es-ai/migration-guard"><img src="https://agentmods.dev/badge/skills/brayandiazc/project-starter-template-es-ai/migration-guard/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/brayandiazc/project-starter-template-es-ai/migration-guard"><img src="https://agentmods.dev/badge/skills/brayandiazc/project-starter-template-es-ai/migration-guard.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.00090 | $0.00535 |
| Opus 5 | $0.00045 | $0.00267 |
| Sonnet 5 | $0.00018 | $0.00107 |
| Haiku 4.5 | $0.00009 | $0.00053 |
Grade A, and why
migration-guard 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 3d 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
Revisa la migración que indique la persona (o la del diff actual) en busca de riesgos.
- Lee
docs/conventions/database.mdpara las reglas de migración del proyecto (nomenclatura, reversibilidad, estrategia de índices, tipos de columna permitidos) ydocs/architecture/database.mdpara el modelo de datos actual que toca. - Verifica la reversibilidad: existe un
down/rollback que funcione, o el cambio está documentado explícitamente como irreversible con su justificación. - Revisa la pérdida de datos: eliminar columnas/tablas, reducir tipos o añadir
una columna
NOT NULLsin valor por defecto/backfill. Marca cualquier paso destructivo. - Revisa la compatibilidad hacia atrás para despliegues sin downtime: ¿pueden convivir el código viejo y el nuevo con el nuevo esquema durante el rollout? Prefiere expandir → migrar → contraer en vez de un cambio rompedor de un solo paso.
- Revisa bloqueos / tablas grandes: operaciones que reescriben o bloquean por mucho tiempo tablas grandes (p. ej. añadir una columna not-null, ciertos índices). Sugiere la variante segura para la base de datos del proyecto.
- Confirma un plan de rollback y que la migración sea idempotente / segura de reintentar cuando la herramienta lo permita.
Salida: un veredicto breve (segura / no segura), los riesgos concretos encontrados y
los cambios mínimos para hacerla segura. Si la decisión es relevante (p. ej. una
migración irreversible), recomienda registrar un ADR en
docs/decisions/.
NO ejecutes la migración. NO relajes las reglas de base de datos del proyecto para que una migración pase — corrige la migración en su lugar.
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.
- 3d ago Changed · -2 lines a6de81dbb39b
- 10d ago First seen · 36 lines · 90 tokens per session scan A 7185e83b5b0a
migration-guard is a skill published in the GitHub repository brayandiazc/project-starter-template-es-ai (15 stars, last pushed 3d ago), licensed MIT. It adds 90 tokens to every session and 535 once invoked, about $0.0005 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-01.
Other skills, from other repositories
chdb-datastore
Skill "chdb-datastore" from ItamarZand88/awesome-agent-conventions, covering chdb datastore — it's just faster pandas, the key insight, change this, to this and everything else stays the same.
posit-ggsql
Skill "posit-ggsql" from ItamarZand88/awesome-agent-conventions, covering ggsql query writer, query structure, pattern a: select → visualise, pattern b: visualise from and data sources.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
migration-review
Review database migration files when a change adds or modifies paths under migrations/. Use it before merge to collect forward, rollback, locking, and data-safety evidence.