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 woliveiras/geremmyas --skill supabase-workflowgit clone --depth 1 https://github.com/woliveiras/geremmyasWrote 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/woliveiras/geremmyas/supabase-workflow)<a href="https://agentmods.dev/skills/woliveiras/geremmyas/supabase-workflow"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/supabase-workflow/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/woliveiras/geremmyas/supabase-workflow"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/supabase-workflow.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.00049 | $0.00316 |
| Opus 5 | $0.00024 | $0.00158 |
| Sonnet 5 | $0.00010 | $0.00063 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
supabase-workflow 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 9d 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 Workflow
Change Supabase with schema, RLS, client access, and generated types kept in sync.
Process
- Identify affected tables, policies, functions, buckets, clients, and user roles.
- Decide whether the change belongs in a migration, checked-in config, Edge Function, or application code.
- For exposed tables, design RLS policies before depending on frontend access.
- Add indexes for policy predicates, joins, filters, and ownership checks.
- Keep service role keys on trusted backends only.
- Regenerate typed clients when schema changes affect application code.
- Test anon/authenticated/service-role paths separately.
- Document rollback or follow-up data backfill when migrations are not easily reversible.
Rules
- Do not use dashboard-only changes as the source of truth.
- Do not expose service role keys to browser or mobile code.
- Do not treat anon or publishable keys as secrets; rely on grants and RLS.
- Write both
USINGandWITH CHECKwhen read and write rules differ.
Output
- Supabase surface affected
- Migration/config/code changes
- RLS and key-safety summary
- Generated type impact
- Verification checklist
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.
- 9d ago First seen · 40 lines · 49 tokens per session scan A 4914a61f7825
supabase-workflow is a skill published in the GitHub repository woliveiras/geremmyas (10 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 316 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 skills, from other repositories
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
platform-custom-field-generate
Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from…
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…
openloomi-api
OpenLoomi ships a local-first HTTP API served from the desktop app (port 3414, fallback 3515). All auth, Memory, AI, RAG, Loop, and Audit data live in a local SQLite database — your data stays on your machine and the OpenLoomi app is the source of truth. The only externally-routed auth path is the Composio OAuth…
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…