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 skills/mnlt/teleport/supabasenpx skills add mnlt/teleport --skill supabasegit clone --depth 1 https://github.com/mnlt/teleportWrote 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/mnlt/teleport/supabase)<a href="https://agentmods.dev/skills/mnlt/teleport/supabase"><img src="https://agentmods.dev/badge/skills/mnlt/teleport/supabase.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.00067 | $0.02040 |
| Opus 5 | $0.00034 | $0.01020 |
| Sonnet 5 | $0.00013 | $0.00408 |
| Haiku 4.5 | $0.00007 | $0.00204 |
Grade B, and why
supabase scanned grade B with 2 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
> That covers the Management API PAT (`SUPABASE_ACCESS_TOKEN`). For per-project keys (`SUPABASE_URL` + `SUPABASE_ANON_KEY` / `SUPABASE_SERVICE_ROLE_KEY`), grab them from your project's dashboard → Settings → API — those Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL \ How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supabase
Direct HTTP against Supabase's REST APIs — no MCP server required. Two distinct API surfaces on different hosts with different auth. Picking the wrong one is the single most common failure mode; internalize the split before sending any request.
Usage
- Use for: Listing projects / fetching API keys, PostgREST table reads/writes, auth admin, storage bucket CRUD.
- Skip for: Concept questions (RLS theory), direct
psqloverpostgres://…, debugging user's supabase-js code, schema design.
Credentials check
# For Management API tasks
[ -n "$SUPABASE_ACCESS_TOKEN" ] && echo "SUPABASE_ACCESS_TOKEN: PRESENT" || echo "SUPABASE_ACCESS_TOKEN: MISSING"
# For Project REST tasks
for v in SUPABASE_URL SUPABASE_ANON_KEY SUPABASE_SERVICE_ROLE_KEY; do
eval "val=\${$v}"
[ -n "$val" ] && echo "$v: PRESENT" || echo "$v: MISSING"
done
Never echo these variable values directly — they would appear in the conversation transcript. Use only the boolean patterns above.
If the credentials for the task are MISSING, respond to the user with EXACTLY this message (do NOT paraphrase, do NOT suggest manual JSON edits for the management PAT):
I need your Supabase credentials. Run this in another terminal:
teleport-setup add-key supabaseThat covers the Management API PAT (
SUPABASE_ACCESS_TOKEN). For per-project keys (SUPABASE_URL+SUPABASE_ANON_KEY/SUPABASE_SERVICE_ROLE_KEY), grab them from your project's dashboard → Settings → API — those still need to be added to~/.claude/settings.local.jsonmanually (not yet covered by add-key).Then restart Claude Code (
/exit, thenclaude) and ask me again.
Do NOT suggest editing ~/.claude/settings.local.json manually for the management PAT. teleport-setup add-key supabase handles it safely with backup + masked input. Stop execution until the user has run the command and restarted.
The two-surface split — read this first
| Surface | Base URL | Auth header(s) | Env vars |
|---|---|---|---|
| Management API | https://api.supabase.com/v1/... |
Authorization: Bearer $SUPABASE_ACCESS_TOKEN |
SUPABASE_ACCESS_TOKEN (personal access token) |
| Per-project REST | $SUPABASE_URL/rest/v1/... |
Both: apikey: $KEY AND Authorization: Bearer $KEY (same value in both) |
SUPABASE_URL + SUPABASE_ANON_KEY or SUPABASE_SERVICE_ROLE_KEY |
| Per-project Auth | $SUPABASE_URL/auth/v1/... |
Same two-header pattern | Same as REST |
| Per-project Storage | $SUPABASE_URL/storage/v1/... |
Same two-header pattern | Same as REST |
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.
- 3d ago First seen · 128 lines · 67 tokens per session scan B 5680d55f494a
supabase is a skill published in the GitHub repository mnlt/teleport (9 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 2,040 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
data-policies
Manage ServiceNow dictionary (sysdictionary), table/field creation, choice lists, dictionary overrides, and sysdatapolicy2 rules that enforce mandatory/read-only/visible field behavior on the data layer.
import-export
Move data in and out of ServiceNow — CSV parsing into import sets, GlideImportSetTransformer runs, CSV/JSON/XML exports, scheduled data sources, bulk update and deleteMultiple safety patterns.
gliderecord-patterns
Write efficient ServiceNow GlideRecord queries — addQuery vs addEncodedQuery, setLimit, GlideAggregate for counts, avoiding N+1 in loops, query operators, and safe CRUD with workflow control.
run402
Provision Postgres + REST API + auth + content-addressed storage + serverless functions + email — paid with x402 USDC on Base. Prototype tier is free on testnet. Use when the user asks to build a webapp, deploy a site, create a database, generate images, or mentions Run402.