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 rahmanef63/si-coder-agent --skill sc-supabasegit clone --depth 1 https://github.com/rahmanef63/si-coder-agentWrote 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/rahmanef63/si-coder-agent/sc-supabase)<a href="https://agentmods.dev/skills/rahmanef63/si-coder-agent/sc-supabase"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-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/rahmanef63/si-coder-agent/sc-supabase"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-supabase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 51 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00067 | $0.00556 |
| Opus 5.5 | $0.00027 | $0.00222 |
| Sonnet 5.5 | $0.00013 | $0.00111 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
sc-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
/sc-supabase — Supabase (STUB)
Status: boilerplate only.
When to use
- Project needs Postgres (relational, complex joins, mature SQL tooling) more than Convex's reactive model.
- Project wants Supabase Auth's social providers without self-hosting JWKS.
- Project already has Supabase migrations.
Scope when implemented
- Provision a new Supabase project via the Management API.
- Apply
supabase/migrations/*.sqlin order. - Deploy Edge Functions from
supabase/functions/. - Generate TypeScript types:
supabase gen types typescript. - Write
NEXT_PUBLIC_SUPABASE_URL+NEXT_PUBLIC_SUPABASE_ANON_KEYto project.env.
Env vars
| Var | Purpose |
|---|---|
SUPABASE_ACCESS_TOKEN |
Personal token, https://supabase.com/dashboard/account/tokens |
SUPABASE_ORG_ID |
Org to create projects under |
Suggested file layout
sc-supabase/
├── SKILL.md
└── scripts/
├── project.js # create + capture project ref + db password
├── migrate.js # apply migrations
├── functions.js # deploy edge functions
└── types.js # generate TS types
Implementation notes
- API base:
https://api.supabase.com/v1 - Auth:
Authorization: Bearer <SUPABASE_ACCESS_TOKEN> - Project creation returns a DB password ONCE — capture it directly into the selected Supabase named connection as a private one-time credential.
- For migrations, the
supabaseCLI may be required as a sub-process — wrap it inlib/supabase.js(TODO).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +6 lines c581fe35ccad
- 1mo ago First seen · 49 lines · 67 tokens per session scan A b41df7c8627e
sc-supabase is a skill published in the GitHub repository rahmanef63/si-coder-agent (13 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 556 once invoked, about $0.0003 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-30.
Other skills, from other repositories
supabase-cli
CLI automation for Supabase development workflows. Provides scripts for migrations, Edge Functions, secrets management, type generation, and SQL execution with safety checks.
devlab-dao-sql-compat
A workflow for finding and fixing SQL dialect differences in the data-access layer of an application. SQL is the language used to query databases, and Oracle, PostgreSQL, and MySQL each have variations; the workflow supports MyBatis, JPA, MyBatis-Plus, and SQLAlchemy.
supabase
Supabase platform standards — Row-Level Security, publishable/anon and secret/servicerole key boundaries, Postgres and Edge functions, Storage, Realtime, and the CLI migration workflow. Use when working with RLS policies, Supabase clients, Edge Functions, or supabase/ migrations. Loads alongside the database…
convex-best-practices
Guidelines for building production-ready Convex apps covering function organization, query patterns, validation, TypeScript usage, error handling, and the Zen of Convex design philosophy.
convex-component-authoring
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management.
convex-realtime
Patterns for building reactive apps including subscription management, optimistic updates, cache behavior, and paginated queries with cursor-based loading.