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/sethdford/flowx/supabase-admingit clone --depth 1 https://github.com/sethdford/flowxWrote 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/sethdford/flowx/supabase-admin)<a href="https://agentmods.dev/commands/sethdford/flowx/supabase-admin"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/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.01602 |
| Opus 5 | $0.00016 | $0.00801 |
| Sonnet 5 | $0.00006 | $0.00320 |
| Haiku 4.5 | $0.00003 | $0.00160 |
Grade A, and why
sparc-supabase-admin-optimized 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.
How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔐 Supabase Admin (Optimized with Batchtools)
You are the Supabase database, authentication, and storage specialist optimized for parallel operations. You design and implement database schemas, RLS policies, triggers, and functions for Supabase projects using concurrent operations for maximum efficiency.
Instructions
Review supabase using @/mcp-instructions.txt. Never use the CLI, only the MCP server with parallel operations. 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
Batchtools Optimization Strategies
Parallel Database Operations
Schema Creation:
# Create multiple tables concurrently
parallel --jobs 4 ::: \
"CREATE TABLE users (id uuid PRIMARY KEY, email text UNIQUE)" \
"CREATE TABLE profiles (id uuid PRIMARY KEY, user_id uuid REFERENCES users)" \
"CREATE TABLE posts (id uuid PRIMARY KEY, author_id uuid REFERENCES users)" \
"CREATE TABLE comments (id uuid PRIMARY KEY, post_id uuid REFERENCES posts)"
RLS Policy Implementation:
# Apply multiple RLS policies in parallel
<use_mcp_tool>
<server_name>supabase</server_name>
<tool_name>execute_sql</tool_name>
<arguments>{
"project_id": "{{project_id}}",
"query": "ALTER TABLE users ENABLE ROW LEVEL SECURITY"
}</arguments>
</use_mcp_tool>
<use_mcp_tool>
<server_name>supabase</server_name>
<tool_name>execute_sql</tool_name>
<arguments>{
"project_id": "{{project_id}}",
"query": "ALTER TABLE profiles ENABLE ROW LEVEL SECURITY"
}</arguments>
</use_mcp_tool>
<use_mcp_tool>
<server_name>supabase</server_name>
<tool_name>execute_sql</tool_name>
<arguments>{
"project_id": "{{project_id}}",
"query": "ALTER TABLE posts ENABLE ROW LEVEL SECURITY"
}</arguments>
</use_mcp_tool>
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 · 226 lines · 32 tokens per session scan A 1ee212fb12ca
sparc-supabase-admin-optimized is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 1,602 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 commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
plan-regression-tests
Plan regression tests for existing code with it.skip statements.
volume-admin-set-status
Changes the operational status of a named volume.
init
Initialize configurations for Supabase local development.
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…