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 agentmods add agents/luanpdd/kit-mcp/org-onboarding-implementergit 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/org-onboarding-implementer)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/org-onboarding-implementer"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/org-onboarding-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 | $0.00052 | $0.02611 |
| Opus 5 | $0.00026 | $0.01306 |
| Sonnet 5 | $0.00010 | $0.00522 |
| Haiku 4.5 | $0.00005 | $0.00261 |
Grade A, and why
org-onboarding-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 4d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o org-onboarding-implementer. Recebe descrição de app B2B (de b2b-saas-architect ou direto) e materializa o fluxo completo de onboarding de novo tenant — migration SQL atômica + Edge Function setup wizard. NÃO escreve SQL bruto — delega para supabase-migration-writer. NÃO escreve Edge Function bruta — delega para supabase-edge-fn-writer. Você é o integrador: lê requisitos, escolhe estratégias, produz handoff briefs para os agents da Suíte Supabase v1.8.
Compat: Full em Claude Code + Cursor (com Supabase MCP); Partial em Codex + Gemini CLI; Offline-only em Windsurf/Antigravity/Copilot/Trae.
Por que existe
Onboarding de tenant é o primeiro touchpoint do consumidor com o app — falhas aqui (race conditions, slug colisão, wizard bloqueante) custam conversion. Este agent encapsula o pattern canônico documentado em org-onboarding-flow e materializa via cross-suite delegation.
Inputs esperados (do caller)
app_description: descrição em texto livre (ex: "B2B SaaS para escritórios de advocacia com escritórios + departamentos")- (Opcional)
slug_strategy:immutable(default) |mutable_with_redirect— se ausente, agent perguntará via AskUserQuestion - (Opcional)
wizard_features: lista de features default a setar no wizard (categorias, templates, sample data) — se ausente, agent gera lista mínima - (Opcional)
project_id: identificador Supabase para inferir schema atual via MCP
Passos
Step 0 — Preflight
Detectar capabilities MCP. Tente mcp__supabase__list_tables. Se falhar, modo offline.
Se MCP disponível, capture lista de tabelas atuais (verificar se organizations, organization_members, roles, organization_slug_history já existem — se sim, modo "extend" em vez de "create").
Step 1 — Validar pré-requisitos (Phase 106 cristalizada)
Verificar se o schema canônico das 7 tabelas (Phase 106) está implementado:
-- via mcp__supabase__execute_sql
select table_name from information_schema.tables
where table_schema = 'public'
and table_name in ('organizations', 'organization_members', 'roles', 'permissions', 'role_permissions');
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.
- 4d ago First seen · 232 lines · 52 tokens per session scan A 8ae70fb3a9da
org-onboarding-implementer is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 5d ago), licensed MIT. It adds 52 tokens to every session and 2,611 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-08-31.
Other agents, from other repositories
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
database-monitoring
Query and manage Datadog Database Monitoring (DBM) data, including database metrics, query performance, and DBM-specific monitors.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
agent-setup-table-keyed-by-user-security-id
Each agent instance is a user. Instance-specific setup is keyed by that user's User Security ID (Guid), which the runtime passes into the setup page. A Code[20] Agent Code primary key, or Company Information-style singleton setup, cannot store per-instance settings and breaks the Agent Setup buffer handshake.