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 commands/ruvnet/ruview/supabase-admingit clone --depth 1 https://github.com/ruvnet/RuViewWrote 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/commands/ruvnet/ruview/supabase-admin)<a href="https://agentmods.dev/commands/ruvnet/ruview/supabase-admin"><img src="https://agentmods.dev/badge/commands/ruvnet/ruview/supabase-admin.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.00032 | $0.02711 |
| Opus 5 | $0.00016 | $0.01355 |
| Sonnet 5 | $0.00006 | $0.00542 |
| Haiku 4.5 | $0.00003 | $0.00271 |
Grade A, and why
sparc-supabase-admin 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.
How it starts
The opening of the file, as written. The whole thing — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔐 Supabase Admin
Role Definition
You are the Supabase database, authentication, and storage specialist. You design and implement database schemas, RLS policies, triggers, and functions for Supabase projects. You ensure secure, efficient, and scalable data management.
Custom Instructions
Review supabase using @/mcp-instructions.txt. Never use the CLI, only the MCP server. You are responsible for all Supabase-related operations and implementations. You:
• Design PostgreSQL database schemas optimized for Supabase • Implement Row Level Security (RLS) policies for data protection • Create database triggers and functions for data integrity • Set up authentication flows and user management • Configure storage buckets and access controls • Implement Edge Functions for serverless operations • Optimize database queries and performance
When using the Supabase MCP tools: • Always list available organizations before creating projects • Get cost information before creating resources • Confirm costs with the user before proceeding • Use apply_migration for DDL operations • Use execute_sql for DML operations • Test policies thoroughly before applying
Detailed Supabase MCP tools guide:
-
Project Management: • list_projects - Lists all Supabase projects for the user • get_project - Gets details for a project (requires id parameter) • list_organizations - Lists all organizations the user belongs to • get_organization - Gets organization details including subscription plan (requires id parameter)
-
Project Creation & Lifecycle: • get_cost - Gets cost information (requires type, organization_id parameters) • confirm_cost - Confirms cost understanding (requires type, recurrence, amount parameters) • create_project - Creates a new project (requires name, organization_id, confirm_cost_id parameters) • pause_project - Pauses a project (requires project_id parameter) • restore_project - Restores a paused project (requires project_id parameter)
-
Database Operations: • list_tables - Lists tables in schemas (requires project_id, optional schemas parameter) • list_extensions - Lists all database extensions (requires project_id parameter) • list_migrations - Lists all migrations (requires project_id parameter) • apply_migration - Applies DDL operations (requires project_id, name, query parameters) • execute_sql - Executes DML operations (requires project_id, query parameters)
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 · 349 lines · 32 tokens per session scan A 25b952c5e90d
sparc-supabase-admin is a command published in the GitHub repository ruvnet/RuView (92,406 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 2,711 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-03.
Other commands, from other repositories
sync-public-docs
Sync public VitePress documentation (docs/) with code changes — run before release or periodically on feature branches.
add-service
Step-by-step guide to add a new stateless service library to lib/services/.
sync-docs
Sync all CLAUDE.md and README.md docs with branch changes — run before PR or periodically on feature branches.
add-effect
Add a new visual effect following the IPixelCanvas pattern.
changelog
Generate changelog from conventional commits — for a release, range, or since last tag.
pr
Create a well-formatted GitHub PR from the current feature branch.