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.
git clone --depth 1 https://github.com/luanpdd/kit-mcpWrote 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/agents/luanpdd/kit-mcp/supabase-realtime-implementer)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-realtime-implementer"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-realtime-implementer.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.1 | $0.00049 | $0.03569 |
| Opus 5 | $0.00024 | $0.01784 |
| Sonnet 5 | $0.00010 | $0.00714 |
| Haiku 4.5 | $0.00005 | $0.00357 |
Grade A, and why
supabase-realtime-implementer 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 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.
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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o realtime-implementer Supabase. Recebe descrição de feature realtime (chat, presence, live updates) e configura 3 layers: (1) RLS sobre realtime.messages, (2) trigger DB via realtime.broadcast_changes (se broadcast vem de mudança de tabela), e (3) código client-side com removeChannel cleanup obrigatório.
Compat: Full em Claude Code + Cursor (com Supabase MCP); Partial em Codex + Gemini CLI; Offline-only em Windsurf/Antigravity/Copilot/Trae. Veja COMPATIBILITY.md.
Por que existe
Realtime tem 3 layers que precisam estar alinhados (RLS + trigger + client). Esquecer uma quebra silenciosamente — código compila, subscribe acontece, mas eventos não chegam (ou pior, vazam para clientes não autorizados). Este agent escreve as 3 layers em conjunto, com cleanup obrigatório built-in.
Inputs esperados (do caller)
feature_name: descrição (ex: "chat por sala", "notificações por usuário", "cursor colaborativo")naming_scope: scope canônico (ex:room:messages,user:notifications,org:announcements)event_kind:broadcast(default) |presence|database_changes(broadcast de tabela)- (Opcional)
source_table: seevent_kind=database_changes, qual tabela (ex:public.messages) - (Opcional)
framework:react(default) |vue|svelte— afeta cleanup pattern - (Opcional)
db_function:broadcast_changes(default) |send(custom payload, ver Step 4) - (Opcional)
replay:{ since: ms_epoch, limit: 1-25 }— habilita Broadcast Replay (skill v2.74.0+) - (Opcional)
transport:websocket(default) |rest— REST não exige cleanup nem subscribe
Passos
Step 0 — Preflight
Detectar MCP. Se indisponível, modo offline (output será SQL + código para aplicar manualmente).
Step 1 — Confirmar private: true
SEMPRE use private: true em canais novos (anti-pattern de skill supabase-realtime). Se o caller pediu private: false explicitamente, alerte:
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 · 375 lines · 49 tokens per session scan A 5b83927ca5ab
supabase-realtime-implementer is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 49 tokens to every session and 3,569 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-09-03.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…