Borrowing it
Nothing to install: this file belongs to Terrabase-in/terrabase. 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/Terrabase-in/terrabase/main/.claude/skills/terrabase-db-changes/SKILL.mdgit clone --depth 1 https://github.com/Terrabase-in/terrabaseWrote 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/terrabase-in/terrabase/terrabase-db-changes)<a href="https://agentmods.dev/skills/terrabase-in/terrabase/terrabase-db-changes"><img src="https://agentmods.dev/badge/skills/terrabase-in/terrabase/terrabase-db-changes/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/terrabase-in/terrabase/terrabase-db-changes"><img src="https://agentmods.dev/badge/skills/terrabase-in/terrabase/terrabase-db-changes.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.00098 | $0.00682 |
| Opus 5 | $0.00049 | $0.00341 |
| Sonnet 5 | $0.00020 | $0.00136 |
| Haiku 4.5 | $0.00010 | $0.00068 |
Grade A, and why
terrabase-db-changes 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 8d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
terrabase DB changes
Route database schema/migration work through the terrabase MCP tools so every change gets a deterministic safety verdict, an advisory local-Qwen plan, and an activity record — instead of hand-writing and applying raw SQL.
When this applies
BOTH must hold:
- The task involves Postgres DDL/DML: CREATE/ALTER/DROP of tables, columns, indexes, constraints, types; backfills; or migrations.
- The calling project declares a terrabase target — a
TERRABASE_DATABASE_URLentry in the project's.env(or.env.local).
If the project has no declared target, DO NOT use this skill — the target
resolution will refuse (NO_TARGET) and you must not route the change to any
other database. Proceed with the project's own workflow instead.
Procedure
- Propose. Call
propose_migrationwith the change. Pass the absolute project root asprojectPathso the change is attributed and resolved against this project's target — never a global one. Provide either:sql: the migration SQL, orintent: a natural-language description (terrabase drafts SQL with Qwen).
- Review. Read the returned
report(the deterministic verdict is authoritative) and thePlan:summary. Surface to the user briefly: the verdict, one-line summary, and anyblock/warndiagnostics with their safe-rewrite suggestions. - Apply only after explicit user approval. If the user approves, call
apply_migrationwith theproposalIdandapprovalTokenfrom step 1. Ablockverdict additionally requiresforce: true— never set it without the user's explicit say-so. - Report. State what landed (or that it was proposed-only), and note that the activity is visible project-wise in the terrabase desktop app.
Rules
- The deterministic safety engine — never the LLM — decides safety. Do not
override a
blockverdict on the model's say-so. - Never pass an explicit
dsn; rely onprojectPathresolution so a change can only reach the project's own declared database. - Keep the user-facing summary short: verdict, summary, and the actionable diagnostics only.
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.
- 8d ago First seen · 59 lines · 98 tokens per session scan A d288dc764621
terrabase-db-changes is a skill published in the GitHub repository Terrabase-in/terrabase (0 stars, last pushed 6d ago), licensed Apache-2.0. It adds 98 tokens to every session and 682 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-08-31.
Other skills, from other repositories
supabase
Supabase migration safety, local testing workflow, grant requirements, fallback observability, and health endpoint patterns.
rc-sqlx
Implements and reviews SQLx 0.8+ with PostgreSQL in Rust — PgPool, query/queryas, bind parameters, transactions, migrations, compile-time macros, database tests. Use when writing or changing SQLx/Postgres access from Rust. Do not use for Axum routing alone (rc-axum), SvelteKit (rc-sveltekit), Rust idioms (rc-rust), or…
rc-sql
Relational query and schema work — indexes, EXPLAIN, N+1, modeling. Read-only by default. Use when reviewing SQL. Not for infra admin.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
postgres-patterns
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.
alembic-migration
Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.