Borrowing it
Nothing to install: this file belongs to systemowiec/ai-agents-workspace-starter. 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/systemowiec/ai-agents-workspace-starter/main/.agents/skills/database-migration/SKILL.mdgit clone --depth 1 https://github.com/systemowiec/ai-agents-workspace-starterWrote 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/systemowiec/ai-agents-workspace-starter/database-migration)<a href="https://agentmods.dev/skills/systemowiec/ai-agents-workspace-starter/database-migration"><img src="https://agentmods.dev/badge/skills/systemowiec/ai-agents-workspace-starter/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.1 | $0.00040 | $0.00717 |
| Opus 5 | $0.00020 | $0.00358 |
| Sonnet 5 | $0.00008 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
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 7d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Database Migration
Database migration procedures using Alembic with SQLAlchemy async.
Creating a New Migration
1. Define or Update the Model
Create or update SQLAlchemy model in backend/app/infrastructure/adapters/db/models.py.
Ensure the model inherits from Base and has proper __tablename__.
1b. Check the migration naming convention
Before generating a migration, the agent MUST inspect existing files in backend/alembic/versions/.
Rules:
- If the project uses sequential numbering, e.g.
0001_...,0002_..., the agent MUST continue the same convention - If the project uses any other established naming scheme, the agent MUST preserve it exactly
- The agent MUST NOT invent its own migration filename format
- The agent MUST NOT create random, generic, or low-signal names such as
update,fix,changes,test, ormisc - The migration description must be short, technical, descriptive, and in English
- If the repository does not yet contain migrations or an explicit convention, the agent must ask the user which format should be used
2. Generate Migration
# Auto-generate from model changes
make db-migrate msg="add users table"
# Equivalent Docker command:
# docker compose -f infra/docker-compose.yml exec backend alembic revision --autogenerate -m "add users table"
3. Review Migration
Check the generated file in backend/alembic/versions/:
- Are all columns correct?
- Are indexes and constraints included?
- Does the migration handle
upgrade()anddowngrade()properly? - Is the MariaDB dialect compatible? (no PostgreSQL-specific syntax)
4. Apply Migration
# Apply all pending migrations
make db-upgrade
# Equivalent: alembic upgrade head
5. Verify
# Check current migration status
make db-shell
# Then: SHOW TABLES; DESCRIBE my_table;
Rollback
# Rollback last migration
make db-downgrade
# Equivalent: alembic downgrade -1
Data Migrations
For seed data or data transformations, use op.execute() with raw SQL in upgrade() and matching DELETE in downgrade().
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.
- 7d ago First seen · 95 lines · 40 tokens per session scan A 185978485b5c
database-migration is a skill published in the GitHub repository systemowiec/ai-agents-workspace-starter (2 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 717 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-31.
Other skills, from other repositories
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.