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 piyushverma0/android-agent-skills --skill supabase-androidgit clone --depth 1 https://github.com/piyushverma0/android-agent-skillsWrote 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/piyushverma0/android-agent-skills/supabase-android)<a href="https://agentmods.dev/skills/piyushverma0/android-agent-skills/supabase-android"><img src="https://agentmods.dev/badge/skills/piyushverma0/android-agent-skills/supabase-android/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/piyushverma0/android-agent-skills/supabase-android"><img src="https://agentmods.dev/badge/skills/piyushverma0/android-agent-skills/supabase-android.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.00115 | $0.01822 |
| Opus 5 | $0.00057 | $0.00911 |
| Sonnet 5 | $0.00023 | $0.00364 |
| Haiku 4.5 | $0.00012 | $0.00182 |
Grade A, and why
supabase-android 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.
How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supabase Android (supabase-kt)
Setup
[versions]
supabase = "3.0.2"
ktor = "3.0.1"
[libraries]
supabase-bom = { group = "io.github.jan-tennert.supabase", name = "bom", version.ref = "supabase" }
supabase-postgrest = { group = "io.github.jan-tennert.supabase", name = "postgrest-kt" }
supabase-auth = { group = "io.github.jan-tennert.supabase", name = "auth-kt" }
supabase-realtime = { group = "io.github.jan-tennert.supabase", name = "realtime-kt" }
supabase-storage = { group = "io.github.jan-tennert.supabase", name = "storage-kt" }
supabase-functions = { group = "io.github.jan-tennert.supabase", name = "functions-kt" }
ktor-android = { group = "io.ktor", name = "ktor-client-android", version.ref = "ktor" }
implementation(platform(libs.supabase.bom))
implementation(libs.supabase.postgrest)
implementation(libs.supabase.auth)
implementation(libs.supabase.realtime)
implementation(libs.supabase.functions)
implementation(libs.ktor.android)
Rule 1: Client initialization — the #1 mistake
// ✅ Correct Supabase client setup
@Module @InstallIn(SingletonComponent::class)
object SupabaseModule {
@Provides @Singleton
fun provideSupabaseClient(): SupabaseClient = createSupabaseClient(
supabaseUrl = BuildConfig.SUPABASE_URL,
supabaseKey = BuildConfig.SUPABASE_ANON_KEY
) {
install(Auth) {
scheme = "myapp"
host = "callback"
}
install(Postgrest)
install(Realtime)
install(Storage)
install(Functions)
}
}
Rule 2: Auth — the UnauthorizedRestException fix
// THE most common Supabase Android bug — fixed here permanently
// ❌ Wrong — causes UnauthorizedRestException on Edge Functions
val client = createSupabaseClient(url, anonKey) {
install(Auth) // persistSession defaults to true — getUser() returns null
}
val user = client.auth.currentUserOrNull() // null after hot restart
// ✅ Correct — when calling Edge Functions with user JWT
suspend fun callSecureEdgeFunction(jwt: String): MyResponse {
val userClient = createSupabaseClient(supabaseUrl, supabaseAnonKey) {
install(Auth) {
persistSession = false // ← REQUIRED for JWT passthrough
}
install(Functions)
}
userClient.auth.getUser(jwt) // ← pass jwt directly, always
return userClient.functions.invoke("my-function")
}
// ✅ Standard auth — sign in and observe session
class AuthRepositoryImpl @Inject constructor(
private val supabase: SupabaseClient
) : AuthRepository {
override val sessionStatus: Flow<SessionStatus>
get() = supabase.auth.sessionStatus
override suspend fun signIn(email: String, password: String): Result<Unit> = runCatching {
supabase.auth.signInWith(Email) {
this.email = email
this.password = password
}
}
override suspend fun signUp(email: String, password: String): Result<Unit> = runCatching {
supabase.auth.signUpWith(Email) {
this.email = email
this.password = password
}
}
override suspend fun signOut() { supabase.auth.signOut() }
override fun currentUser(): UserInfo? = supabase.auth.currentUserOrNull()
}
What ships with it
16 files 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.
- .gitkeep 0 B
- metadata.json 653 B
- references/.gitkeep 0 B
- references/auth-flows.md 2.7 KB
- references/edge-functions.md 3.1 KB
- rules/auth-jwt-edge-function-pattern.md 3.7 KB
- rules/auth-session-state.md 3.5 KB
- rules/database-queries.md 3.8 KB
- rules/edge-function-structure.md 5.1 KB
- rules/error-handling.md 4.3 KB
- rules/functions-invoke-android.md 4.6 KB
- rules/realtime-subscriptions.md 4.0 KB
- rules/repository-pattern.md 4.3 KB
- rules/sdk-setup-hilt.md 3.2 KB
- rules/security-rls-keys.md 3.2 KB
- rules/storage-upload-download.md 3.3 KB
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 · 236 lines · 115 tokens per session scan A 7fcebfc84a25
supabase-android is a skill published in the GitHub repository piyushverma0/android-agent-skills (15 stars, last pushed 4mo ago), licensed MIT. It adds 115 tokens to every session and 1,822 once invoked, about $0.0006 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-30.
Other skills, from other repositories
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
Debroid CLI Debugger
Orchestrate headless Android debugging via JDWP. ACTIVATE this skill whenever asked to debug an Android application, set line or exception breakpoints, inspect runtime variables or Jetpack Compose state, step through execution, evaluate live expressions, watch fields, or diagnose runtime crashes.
maui-networking-offline-data
Build MAUI networking and offline data. USE FOR: typed HttpClient, JSON serialization, Android 10.0.2.2, iOS simulator localhost, LAN/dev-tunnel fallback, debug cleartext, offline-first screens, SQLite/EF Core sync metadata, queues, encryption decisions, retries, cancellation. DO NOT USE FOR: auth redirects, Aspire…
maui-aspire-client
Connect MAUI apps to Aspire-hosted APIs. USE FOR: AddServiceDiscovery, typed HttpClient, https+http://apiservice, missing AppHost config on devices, Android emulator 10.0.2.2, iOS simulator localhost, physical-device LAN/dev-tunnel fallbacks, dev certs, Bearer handlers, debug-only cleartext. DO NOT USE FOR: offline…
network-tracing
Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.
state-sync
When implementing offline-first features, handling optimistic updates, or building sync queues.