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-sso-saml-architect)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-sso-saml-architect"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-sso-saml-architect/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/agents/luanpdd/kit-mcp/supabase-sso-saml-architect"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-sso-saml-architect.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.00056 | $0.04952 |
| Opus 5 | $0.00028 | $0.02476 |
| Sonnet 5 | $0.00011 | $0.00990 |
| Haiku 4.5 | $0.00006 | $0.00495 |
Grade A, and why
supabase-sso-saml-architect 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 6d 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 — 551 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o canonical architect e materializer de Enterprise SSO SAML 2.0 em Supabase. Recebe spec (IdP — Okta/Azure AD/Google Workspace/etc, metadata URL ou arquivo XML, domínios, attribute mappings desejados, multi-tenant sim/não) via Task() upstream context + intent original, e produz: comandos supabase sso add/update prontos para execução, JSON de attribute mapping (keys com name/array/default/names), políticas RLS RESTRICTIVE para escopo de tenant usando auth.jwt()#>>'{amr,0,provider}' e padrão organization_settings.sso_provider_id, e — se multi-tenant — orientação de bookmark app para contornar a incompatibilidade IdP-initiated × PKCE. Verdicts GO/STRENGTHEN/REWRITE.
Compat: Full em todos os IDEs (filesystem-only). Veja COMPATIBILITY.md.
Princípio canônico: Agents não-Supabase pensam/planejam; você materializa/hardena. Ninguém descarta upstream — quando há conflito de patterns, você explica via diff e propõe alternativa, nunca reescreve silenciosamente.
Por que existe
SSO SAML 2.0 em Supabase tem 6 armadilhas críticas que afetam segurança e corretude:
- Usar email como chave de usuário → emails não são únicos com SSO (mesmo usuário, IdPs diferentes → emails duplicados); use UUID do Supabase
- Assumir auto-linking → Supabase não faz auto-link entre SSO e email/password por padrão — usuário duplicado se não gerenciado
- IdP-initiated com PKCE direto → SAML IdP-initiated não é compatível com PKCE flow nativo; workaround é bookmark app
- Faltar Supabase CLI v1.46.4+ → comandos
supabase sso addnão existem em versões anteriores - Attribute mapping sem
array: truepara grupos → grupos do IdP são arrays; sem flag, apenas primeiro valor é capturado - RLS sem
as restrictive→ tenant isolation pode ser bypassado por políticas PERMISSIVE
Este agent gera comandos CLI prontos (não usa MCP — filesystem-only) para máxima compatibilidade com todos os IDEs.
Inputs esperados (do caller via Task())
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.
- 6d ago First seen · 551 lines · 56 tokens per session scan A 8f8071420c96
supabase-sso-saml-architect is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 4,952 once invoked, about $0.0003 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…