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 agentmods add skills/willdady/platypus/database-schema-changesnpx skills add willdady/platypus --skill database-schema-changesgit clone --depth 1 https://github.com/willdady/platypusWhat 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 | $0.00037 | $0.00493 |
| Opus 5 | $0.00018 | $0.00246 |
| Sonnet 5 | $0.00007 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
database-schema-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 today.
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
Database Schema Changes
Push is for your machine; generate is what ships. Both, every time. A push with no generate leaves a dev database that works and a production deploy that never receives the change — and nothing local tells you, because your own database is already correct.
Steps
-
Edit the schema — the backend's Drizzle schema module, where the tables are declared.
-
Push it to your dev database. Needs
pnpm devup, since the push talks to a live Postgres:pnpm drizzle-kit-push -
Generate the migration. Production applies numbered
.sqlmigrations, not your schema file, so this is the step that carries the change out of your machine:pnpm drizzle-kit-generate
Done when git status shows three new or modified artefacts beside your
schema edit: a numbered .sql migration, its snapshot, and an appended journal
entry. All of them are committed, in the same commit as the schema change.
Data changes
Generate writes DDL — it reads your schema and diffs it. A backfill, a re-shaping of existing rows, or anything else that needs to reason about data is yours to write into the generated migration by hand.
Dev never runs it: the push flow applies DDL only and skips migration files entirely, so a hand-written backfill is invisible until production. Apply the equivalent change to your own database by hand and say so on the PR.
Auth tables
better-auth owns the auth tables — do not hand-edit that generated schema. When you change the auth configuration, regenerate it, then treat the result as a normal schema change and continue from step 2:
pnpm --dir apps/backend dlx @better-auth/cli@latest generate \
--config ./src/auth.ts --output ./src/db/auth-schema.ts --yes
(The paths inside that command are arguments the CLI needs, not references to look up.)
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.
- today First seen · 60 lines · 37 tokens per session scan A 8ace1c0a7d7e
database-schema-changes is a skill published in the GitHub repository willdady/platypus (69 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 493 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-09-01.
Other skills, from other repositories
largest-files-finder
List the top 3 largest files in a given directory.
extract-action-items
Extract a list of action items with owners and deadlines from a meeting transcript.
skill-structure-advisor
Helps you choose the right design pattern and structure for a new skill.
cross-border-customer-service-brief
Cluster refund, return, complaint, and bad-review notes into a daily support brief with response guidance and escalation hints.
cross-border-listing-image-layout-audit
Audit listing image and layout notes — first-impression hero, info hierarchy, lifestyle vs studio, copy density, trust signals, compliance — into a follow-up checklist.
cross-border-price-match-review
Cluster competitor price, coupon, shipping, and bundle observations into a price-gap review with explicit human-approval guidance.