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 skills add dhaupin/vant --skill vant-skill-supabasegit clone --depth 1 https://github.com/dhaupin/vantWrote 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/skills/dhaupin/vant/vant-skill-supabase)<a href="https://agentmods.dev/skills/dhaupin/vant/vant-skill-supabase"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-supabase/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/skills/dhaupin/vant/vant-skill-supabase"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-supabase.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.00006 | $0.00348 |
| Opus 5.5 | $0.00002 | $0.00139 |
| Sonnet 5.5 | $0.00001 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
supabase 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 1mo 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
Supabase
Backend operations.
When To Use
- PostgreSQL backend
- Auth needed
- Real-time data
- Edge functions
What To Do
1. Connect
# supabase-js
import { createClient } from '@supabase/supabase-js'
const supabase = createClient(
'https://xxx.supabase.co',
'public-anon-key'
)
2. Common Operations
| Operation | What |
|---|---|
| select | Query data |
| insert | Insert data |
| update | Update data |
| delete | Delete data |
| subscribe | Real-time |
3. Auth
// Sign up
const { user, session } = await supabase.auth.signUp({
email: '[email protected]',
password: 'password'
})
// Sign in
const { user, session } = await supabase.auth.signInWithPassword({
email: '[email protected]',
password: 'password'
})
4. Edge Functions
supabase functions serve
supabase functions deploy my-function
Output
## Supabase
| Table | Rows | Status |
|-------|------|--------|
| [name] | [n] | [OK] |
### Functions
- [list]
Role: Supabase Backend
Input: Tables, functions
Output: Working backend
Backend as a service.
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.
- 1mo ago First seen · 93 lines · 6 tokens per session scan A 49505858d40a
supabase is a skill published in the GitHub repository dhaupin/vant (12 stars, last pushed today), licensed MIT. It adds 6 tokens to every session and 348 once invoked, about $0.0000 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 skills, from other repositories
cohesivity
Use Cohesivity for a project backend only after the user explicitly chooses Cohesivity. Installing or reading this optional skill does not authorize bootstrap, deployment, global installs, or feedback.
doris-debug-deployment
Use for Doris FE/BE startup failures, port conflicts, prioritynetworks misrouting, metadir corruption, and ADD/DROP BACKEND issues.
kirby-content-migration
Plans and applies safe Kirby content migrations using runtime content tools, update schemas, and explicit confirmation. Use when users need to rename/move/transform fields, clean up content, or bulk-update pages/files across languages.
backend-architect
Use when implementing server-side logic, designing middleware, integrating databases, or building API endpoints — with TDD and verification discipline.
quarry
Query PostgreSQL, MySQL, Redis and Neptune with Quarry (qy), compare data across environments, maintain reusable queries, and manage connections or the database workbench. Use for database evidence or explicit Quarry tasks, not general database design discussions.
supabase-development-guide
Write Supabase migrations, RLS policies or Edge Functions; configure Deno checks, pgTAP tests, secrets or deployment.