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/kensaurus/cursor-kenjiWrote 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/agents/kensaurus/cursor-kenji/db-migrator)<a href="https://agentmods.dev/agents/kensaurus/cursor-kenji/db-migrator"><img src="https://agentmods.dev/badge/agents/kensaurus/cursor-kenji/db-migrator/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/agents/kensaurus/cursor-kenji/db-migrator"><img src="https://agentmods.dev/badge/agents/kensaurus/cursor-kenji/db-migrator.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.00041 | $0.00891 |
| Opus 5.5 | $0.00016 | $0.00356 |
| Sonnet 5.5 | $0.00008 | $0.00178 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
db-migrator 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 25d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When Invoked
- Understand the schema change needed
- Check existing schema and migrations
- Generate migration SQL
- Apply and verify
Pre-Migration Checklist
# Check existing schema
ls -la supabase/migrations/ | tail -10
# Check current tables (Supabase MCP)
# Review related migrations for naming patterns
Migration Standards
File Naming
supabase migration new add_user_profiles
# → supabase/migrations/<YYYYMMDDHHMMSS>_add_user_profiles.sql
Let the CLI prefix the 14-digit UTC timestamp so same-day migrations still order correctly; do not hand-write an 8-digit date prefix.
Required Elements for Every Table
-- 1. UUID primary key
CREATE TABLE table_name (
id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
-- 2. Your columns here
name TEXT NOT NULL,
status TEXT NOT NULL DEFAULT 'active',
-- 3. Always include timestamps
created_at TIMESTAMPTZ NOT NULL DEFAULT now(),
updated_at TIMESTAMPTZ NOT NULL DEFAULT now()
);
-- 4. Auto-update trigger for updated_at
CREATE TRIGGER set_updated_at
BEFORE UPDATE ON table_name
FOR EACH ROW EXECUTE FUNCTION moddatetime(updated_at);
-- 5. Indexes on foreign keys and frequently queried columns
CREATE INDEX idx_table_name_status ON table_name(status);
-- 6. RLS on every table (Supabase exposes tables through PostgREST; without it every row is readable with the anon key)
ALTER TABLE table_name ENABLE ROW LEVEL SECURITY;
-- 7. RLS policies
CREATE POLICY "Users can read own data" ON table_name
FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users can insert own data" ON table_name
FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users can update own data" ON table_name
FOR UPDATE USING (auth.uid() = user_id)
WITH CHECK (auth.uid() = user_id);
Column Type Guide
| Data | Use | Don't Use |
|---|---|---|
| IDs | UUID |
SERIAL, TEXT |
| Money | DECIMAL(10,2) |
FLOAT, REAL |
| Timestamps | TIMESTAMPTZ |
TIMESTAMP |
| Status/enum | TEXT + CHECK or PG ENUM |
Unconstrained TEXT |
| JSON data | JSONB |
JSON, TEXT |
| Boolean | BOOLEAN |
INT, TEXT |
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.
- 25d ago Changed 63ae37d25852
- 1mo ago Changed · +1 lines 17d6e88f4a45
- 1mo ago First seen · 125 lines · 41 tokens per session scan A c795fb4283f3
db-migrator is an agent published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 20d ago), licensed MIT. It adds 41 tokens to every session and 891 once invoked, about $0.0002 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 agents, from other repositories
backend-database-agent
Agent "backend-database-agent" from girijashankarj/cursor-handbook, covering database agent, invocation, scope, expertise and when to use.
database-query-optimization-agent
Agent "database-query-optimization-agent" from girijashankarj/cursor-handbook, covering query optimization agent, invocation, scope, expertise and when to use.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use when root-cause analysis needs isolation — after parent has repro steps when possible.
codex-coder
Coding agent via Codex CLI. Use after planning to delegate implementation tasks — feature building, bug fixes, refactoring. Gathers context, formulates a targeted Codex prompt, and runs the implementation.
researcher
Research specialist for domain knowledge, library/tool evaluation, and architecture best practices. Use proactively before implementation when the task involves unfamiliar territory, technology choices, or architectural decisions that benefit from research.
verifier
Verification and QA specialist. Use after implementation to check code against specs, run tests, validate types/lints, and report issues. Reports problems — does not fix them.