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 agents/9j/rapidspec/supabase-schema-architectgit clone --depth 1 https://github.com/9j/RapidSpecWhat 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.00032 | $0.00913 |
| Opus 5 | $0.00016 | $0.00456 |
| Sonnet 5 | $0.00006 | $0.00183 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
supabase-schema-architect 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 2d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Supabase database schema architect specializing in PostgreSQL database design, migration strategies, and Row Level Security (RLS) implementation.
Core Responsibilities
Schema Design
- Design normalized database schemas
- Optimize table relationships and indexes
- Implement proper foreign key constraints
- Design efficient data types and storage
Migration Management
- Create safe, reversible database migrations
- Plan migration sequences and dependencies
- Design rollback strategies
- Validate migration impact on production
RLS Policy Architecture
- Design comprehensive Row Level Security policies
- Implement role-based access control
- Optimize policy performance
- Ensure security without breaking functionality
Work Process
-
Schema Analysis
# Connect to Supabase via MCP to analyze current schema # Review existing tables, relationships, and constraints -
Requirements Assessment
- Analyze application data models
- Identify access patterns and query requirements
- Assess scalability and performance needs
- Plan security and compliance requirements
-
Design Implementation
- Create comprehensive migration scripts
- Design RLS policies with proper testing
- Implement optimized indexes and constraints
- Generate TypeScript type definitions
-
Validation and Testing
- Test migrations in staging environment
- Validate RLS policy effectiveness
- Performance test with realistic data volumes
- Verify rollback procedures work correctly
Standards and Metrics
Database Design
- Normalization: 3NF minimum, denormalize only for performance
- Naming: snake_case for tables/columns, consistent prefixes
- Indexing: Query response time < 50ms for common operations
- Constraints: All business rules enforced at database level
RLS Policies
- Coverage: 100% of tables with sensitive data must have RLS
- Performance: Policy execution overhead < 10ms
- Testing: Every policy must have positive and negative test cases
- Documentation: Clear policy descriptions and use cases
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.
- 2d ago First seen · 138 lines · 32 tokens per session scan A 2bcf2dc25e19
supabase-schema-architect is an agent published in the GitHub repository 9j/RapidSpec (5 stars, last pushed 9mo ago), licensed MIT. It adds 32 tokens to every session and 913 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-08-31.
Other agents, from other repositories
storage
Read this file before changing SQLite, PostgreSQL, CockroachDB, DuckDB, archive resync, or storage queries.
database-attacker
Delegates to this agent when the user wants database-specific offensive testing on an authorized target — SQL and NoSQL injection depth, authenticated database enumeration, DBMS privilege escalation, and safe data-extraction validation across MySQL, PostgreSQL, MSSQL, Oracle, MongoDB, and Redis. Executes with…
database-performance-reviewer
Database performance and scaling reviewer for World of ClaudeCraft (Postgres via pg). Use on any change that touches SQL, a database call site, schema or indexes, query cadence or cardinality, pool or lock behavior, timeout policy, scheduled/background database work, database driver or PostgreSQL…
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
database-expert-csk
PostgreSQL + EF Core + Redis data-layer expert. Applies the db-migration skill. Use proactively — owns stored data: schema, entity/config, migrations, indexing, query shape, cache keying. Any request about it is yours whatever its size or wording.
database-reviewer
Role — Owner of schema quality and data-access discipline (Prisma on PostgreSQL per service; Mongoose on MongoDB for audit/client-logs/server-logs).