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/super-admin-implementer)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/super-admin-implementer"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/super-admin-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.00053 | $0.03172 |
| Opus 5 | $0.00026 | $0.01586 |
| Sonnet 5 | $0.00011 | $0.00634 |
| Haiku 4.5 | $0.00005 | $0.00317 |
Grade A, and why
super-admin-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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o super-admin-implementer. Materializa platform super-admin (você gerenciando todos tenants) — cross-tenant view, impersonation, ações destrutivas com confirmação, audit obrigatório. ABORTA se audit_log Phase 109 não implementado (BLOCKER ADMIN-03).
Por que existe
Super-admin é poder operacional crítico — implementação inconsistente = ou poder demais sem audit (privilege escalation interna), ou poder limitado que impede suporte real. Este agent garante o pattern canônico (cross-tenant + impersonation TTL + audit obrigatório + dupla confirmação).
Inputs
- (Opcional)
enable_impersonation:true(default) |false - (Opcional)
enable_delete_org:true(default — soft delete) |false - (Opcional)
impersonation_ttl_minutes: default 30
Passos
Step 0 — Preflight + BLOCKER check
Detectar MCP. CRITICAL CHECK — Phase 109 audit_logs implementado:
select exists (
select 1 from information_schema.tables
where table_schema = 'public' and table_name = 'audit_logs'
) as audit_logs_exists,
exists (
select 1 from pg_proc
where proname = 'audit_log' and pronamespace = 'private'::regnamespace
) as audit_function_exists;
Se ambos não existirem → ABORT IMEDIATO:
✗ ERRO BLOCKER ADMIN-03: audit_logs NÃO implementado.
Super-admin sem audit log é compliance gap LGPD + perda de rastreabilidade interna.
Esta phase recusa-se a prosseguir.
Fix: rodar /multi-tenant audit-log "implementar audit log v1.21" PRIMEIRO.
Step 1 — Coletar features via AskUserQuestion
- "Cross-tenant view (Recomendado)" — super_admin pode listar/ler todos tenants via PERMISSIVE policies
- "Impersonation (Recomendado)" — Edge Function com magic link TTL 30min + reason obrigatório
- "Delete org soft" — RPC super_admin_delete_org com dupla confirmação, soft delete (status='archived')
- "Delete org HARD" — Mesma RPC mas DELETE FROM (cascade) — irreversível, requer aprovação dupla explícita
Step 2 — Coletar primeiro super-admin via AskUserQuestion
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 · 290 lines · 53 tokens per session scan A 62aab024bdf9
super-admin-implementer is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 53 tokens to every session and 3,172 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…