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 codeready-toolchain/tarsy --skill db-migration-reviewgit clone --depth 1 https://github.com/codeready-toolchain/tarsyWrote 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/codeready-toolchain/tarsy/db-migration-review)<a href="https://agentmods.dev/skills/codeready-toolchain/tarsy/db-migration-review"><img src="https://agentmods.dev/badge/skills/codeready-toolchain/tarsy/db-migration-review/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/codeready-toolchain/tarsy/db-migration-review"><img src="https://agentmods.dev/badge/skills/codeready-toolchain/tarsy/db-migration-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.00917 |
| Opus 5 | $0.00034 | $0.00458 |
| Sonnet 5 | $0.00014 | $0.00183 |
| Haiku 4.5 | $0.00007 | $0.00092 |
Grade A, and why
db-migration-review 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- openclaw-history-ingest — 86% identical, 228 lines differ
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DB Migration Review
When to Apply
After every make migrate-create run, review the generated .up.sql file before committing. Atlas diffs the Ent schema against a dev database and frequently emits unrelated operations due to schema drift it cannot model.
Known Atlas Drift Patterns
1. Dropping manually-managed partial indexes
Atlas cannot express WHERE clauses in index definitions. Several indexes are created manually in migrations and documented in Ent schema comments. Atlas sees them in the database but not in the Ent schema, so it generates DROP INDEX statements.
Known partial indexes (must never be dropped):
| Index | Table | Created in |
|---|---|---|
agentexecution_stage_id_agent_index_top_level |
agent_executions |
20260225235224_add_orchestrator_sub_agent_fields.up.sql |
agentexecution_parent_execution_id_agent_index_sub_agent |
agent_executions |
20260225235224_add_orchestrator_sub_agent_fields.up.sql |
These enforce sub-agent ordering uniqueness with WHERE parent_execution_id IS NULL / IS NOT NULL clauses. The Ent schema at ent/schema/agentexecution.go documents this explicitly.
Action: Remove any DROP INDEX targeting these indexes.
2. No-op index drop + recreate
Atlas sometimes re-emits a DROP INDEX + CREATE INDEX pair for indexes that already exist with identical definitions. This commonly affects partial unique indexes like sessionscore_session_id.
How to identify: The CREATE INDEX statement after the DROP is identical to what already exists in a prior migration.
Action: Remove the entire drop + recreate pair.
3. Unrelated table modifications
Occasionally Atlas includes ALTER TABLE statements for tables unrelated to the migration's purpose (e.g., adding default values or constraints that were pending in the schema diff).
Action: If the operation is clearly unrelated to the migration's named purpose, remove it. If uncertain, investigate the Ent schema change that caused it.
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 · 75 lines · 68 tokens per session scan A 7a2eb253f712
db-migration-review is a skill published in the GitHub repository codeready-toolchain/tarsy (10 stars, last pushed today), licensed Apache-2.0. It adds 68 tokens to every session and 917 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
code-review-excellence
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
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.
sql-optimization-patterns
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
multi-reviewer-patterns
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
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.