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.
git clone --depth 1 https://github.com/BetterTyped/hype-stackWrote 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/rules/bettertyped/hype-stack/database-migrations)<a href="https://agentmods.dev/rules/bettertyped/hype-stack/database-migrations"><img src="https://agentmods.dev/badge/rules/bettertyped/hype-stack/database-migrations/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/rules/bettertyped/hype-stack/database-migrations"><img src="https://agentmods.dev/badge/rules/bettertyped/hype-stack/database-migrations.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.00025 | $0.00346 |
| Opus 5.5 | $0.00010 | $0.00138 |
| Sonnet 5.5 | $0.00005 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
database-migrations 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 1mo 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.
What it actually says
Database Migrations
Schema changes follow one workflow. All commands run in apps/backend (or via pnpm --filter @hype-stack/backend <script>).
- Edit
schema.prisma— the single source of truth for database structure. - Create the migration:
pnpm migration:create(runsprisma migrate dev— prompts for a name and applies it to the dev DB). - Regenerate the client:
pnpm generate(Prisma client + message compilation + type declarations). - Sync the test database before running integration tests:
pnpm test:setup(starts the test Docker services, applies migrations, regenerates the client against the test DB). Usepnpm test:cleanto tear it down.
Rules
- Never edit an already-applied migration file — create a new migration instead.
- Never change the database schema outside a migration (no manual SQL against dev/prod).
- Deploying migrations uses
pnpm migration:latest(prisma migrate deploy);pnpm migration:resetandpnpm rebuild-dbare destructive dev-only resets. - Remember the ORM split: Prisma owns schema and inserts, Kysely owns query building — a schema change usually touches both the Prisma schema and the Kysely types generated from it.
- After a schema change, update the affected
db/queries/db/mutationsfunctions and their integration tests in the same change.
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.
- 1mo ago First seen · 22 lines · 25 tokens per session scan A c1f4878a17fc
database-migrations is a cursor rule published in the GitHub repository BetterTyped/hype-stack (12 stars, last pushed 15d ago), licensed MIT. It adds 25 tokens to every session and 346 once invoked, about $0.0001 per session on Opus 5.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 cursor rules, from other repositories
do-not-drop-local-db
Never drop or recreate local databases without explicit user approval.
backend-architecture
The backend is built on Supabase, providing PostgreSQL database, authentication, and Edge Functions for serverless API endpoints.
database-workflow
Cursor rule "database-workflow" from Adam-CAD/CADAM, covering database workflow rules, database schema changes, never create manual migrations, schema file management and migration generation process.
server-actions
Server Action, service and tenancy contract.
database-design
Database schema design patterns for Supabase with proper types and relationships.
supabase-auth-security
Supabase auth security — enforces getUser() over getSession() on the server.