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 ivanhoinacki/team-exp-claude-config --skill validate-migrationgit clone --depth 1 https://github.com/ivanhoinacki/team-exp-claude-configWrote 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/ivanhoinacki/team-exp-claude-config/validate-migration)<a href="https://agentmods.dev/skills/ivanhoinacki/team-exp-claude-config/validate-migration"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/validate-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/ivanhoinacki/team-exp-claude-config/validate-migration"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/validate-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.00064 | $0.03307 |
| Opus 5 | $0.00032 | $0.01654 |
| Sonnet 5 | $0.00013 | $0.00661 |
| Haiku 4.5 | $0.00006 | $0.00331 |
Grade A, and why
validate-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 9d 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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 0: Vault RAG (MANDATORY, BEFORE any Read/Grep)
You MUST call query_vault(query, service_filter) BEFORE reading codebase files or external sources. This is enforced by hook. No exceptions.
Validate Migration
Working Directories
- Obsidian workspace:
__VAULT_ROOT__ - Codebase:
__CODEBASE_ROOT__
Common Agent Mistakes
- No rollback plan: Approving a migration without verifying
down()exists and is correct. Every migration MUST have a working rollback or explicit acknowledgment of irreversibility. - Missing CONCURRENTLY: Not flagging
CREATE INDEXwithoutCONCURRENTLYon any table. This locks the table for writes during index creation. - Ignoring dual-database (svc-experiences): Validating the migration SQL but not reminding about the dual-database requirement. Both dev and spec databases need migration.
- Underestimating table size: Not checking the large table risk list before approving an ALTER TABLE. Always cross-reference Phase 2 table.
- Single-step risky operations: Not suggesting zero-downtime recipes for column renames, type changes, or constraint additions on large tables. Always recommend the multi-step approach.
- Transaction + CONCURRENTLY conflict: Not catching
CREATE INDEX CONCURRENTLYinside a transaction. TypeORM wraps migrations in transactions by default.
Phase 0: Discover and Classify
Find migration files
- If
$ARGUMENTSprovided, use that path directly - Otherwise, find migration files in the current branch diff:
GIT_EDITOR=true git diff --name-only main...HEAD | grep -iE "(migrat|\.sql)"
Detect ORM framework
| Service | ORM | Migration format | Location |
|---|---|---|---|
| svc-experiences | TypeORM | TypeScript classes with up()/down() |
src/migration/ |
| svc-order | Sequelize | JS files with up()/down() |
db/migrations/ |
| svc-ee-offer | Sequelize | JS files | db/migrations/ |
| svc-search | Sequelize | JS files | db/migrations/ |
| svc-auth | Prisma | .prisma schema + SQL |
prisma/migrations/ |
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.
- 9d ago First seen · 367 lines · 64 tokens per session scan A a4817fcc783c
validate-migration is a skill published in the GitHub repository ivanhoinacki/team-exp-claude-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 3,307 once invoked, about $0.0003 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
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.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
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.
database-design
Designs database schemas, indexing strategies, query optimization, and migration patterns for SQL and NoSQL databases. Use when designing tables, optimizing queries, fixing N+1 problems, planning migrations, or when asked about database performance, normalization, ORMs, or data modeling.
architect/data-api-design
A guide to designing data models and application programming interfaces (APIs), which are the rules software uses to exchange data.