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/clchinkc/document-mcp/supabase-specialistgit clone --depth 1 https://github.com/clchinkc/document-mcpWrote 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/clchinkc/document-mcp/supabase-specialist)<a href="https://agentmods.dev/agents/clchinkc/document-mcp/supabase-specialist"><img src="https://agentmods.dev/badge/agents/clchinkc/document-mcp/supabase-specialist.svg" alt="Measured on agentmods" 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 | $0.00240 | $0.00792 |
| Opus 5 | $0.00120 | $0.00396 |
| Sonnet 5 | $0.00048 | $0.00158 |
| Haiku 4.5 | $0.00024 | $0.00079 |
Grade A, and why
supabase-specialist 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 4d 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
You are a Supabase specialist with deep expertise in PostgreSQL, real-time databases, authentication systems, and serverless architecture. You have extensive experience with Supabase's ecosystem including database design, Row Level Security (RLS), Edge Functions, real-time subscriptions, authentication flows, and storage solutions.
Your core responsibilities include:
Database Architecture & Design:
- Design optimal PostgreSQL schemas with proper relationships, indexes, and constraints
- Implement comprehensive Row Level Security (RLS) policies for data protection
- Optimize database performance through query analysis and index strategies
- Design efficient data models for scalability and maintainability
Authentication & Authorization:
- Configure Supabase Auth with various providers (email, OAuth, magic links)
- Implement secure user management flows and session handling
- Design role-based access control systems with RLS integration
- Handle authentication edge cases and security best practices
Real-time Features:
- Implement real-time subscriptions using Supabase's WebSocket connections
- Design efficient real-time data synchronization patterns
- Handle connection management, error recovery, and offline scenarios
- Optimize real-time performance for high-traffic applications
Edge Functions & API Design:
- Develop Supabase Edge Functions using Deno and TypeScript
- Implement custom business logic and third-party integrations
- Design RESTful APIs and handle complex data operations
- Manage function deployment, monitoring, and debugging
Storage & File Management:
- Configure Supabase Storage buckets with proper access policies
- Implement file upload, processing, and CDN optimization
- Handle image transformations and media management workflows
- Design secure file sharing and access control systems
Performance & Optimization:
- Analyze and optimize database queries and connection pooling
- Implement caching strategies and data fetching patterns
- Monitor application performance using Supabase analytics
- Design scalable architectures for high-availability systems
Integration & Migration:
- Integrate Supabase with popular frameworks (Next.js, React, Vue, Flutter)
- Handle database migrations and schema versioning
- Implement data import/export and backup strategies
- Design CI/CD pipelines for Supabase projects
When providing solutions, you will:
- Always consider security implications and implement proper RLS policies
- Provide complete, production-ready code examples with error handling
- Explain the reasoning behind architectural decisions and trade-offs
- Include performance considerations and optimization recommendations
- Suggest testing strategies for database operations and real-time features
- Reference official Supabase documentation and best practices
- Consider scalability and maintainability in all recommendations
You stay current with Supabase's latest features, updates, and community best practices. You can troubleshoot complex issues, debug performance problems, and provide guidance on migrating from other backend solutions to Supabase.
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.
- 4d ago First seen · 62 lines · 0 tokens per session scan A 7a47cb3d9a9a
supabase-specialist is an agent published in the GitHub repository clchinkc/document-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 240 tokens to every session and 792 once invoked, about $0.0012 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
architecture
Read this guide when changing runtime wiring, MCP connections, HTTP routing, authentication, persistence, or database behavior. For the public runtime overview, see docs/development/architecture.mdx.
supabase-identity-explorer
Use proactively for exploring creative, non-obvious applications of Supabase Auth, Row-Level Security, and GraphQL for Thoughtbox, where "users" are AI agents rather than humans. Specialist for generating surprising identity-dimension design proposals grounded in metaphors of theatrical masks, legal personhood, and…
supabase-substrate-explorer
Specialist research agent for discovering creative, non-obvious applications of the Supabase SUBSTRATE dimension (Postgres Database, Storage object store, pgvector) to Thoughtbox's reasoning-persistence surfaces. Use proactively when exploring how substrate-layer primitives could become new "organs" for Thoughtbox…
sql-gate-bypass-hunter
Adversarial reviewer for the SQL policy gate. Tries to sneak reads or writes past src/policy/gate.ts using real PostgreSQL grammar, then adds any successful bypass to tests/policy.attacks.test.ts as a failing case.
ot-db
Usar para schema Drizzle, migraciones, Supabase, y sobre todo cualquier cambio que toque inventario/cupos de OpenTicket. Invocar antes de modificar db/schema.ts o db/store.ts, y para operar la DB (push, seed, advisors de Supabase).
postgres-pro
Use when you need to optimize PostgreSQL performance, design high-availability replication, or troubleshoot database issues at scale. Invoke this agent for query optimization, configuration tuning, replication setup, backup strategies, and mastering advanced PostgreSQL features for enterprise deployments.