Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/luanpdd/kit-mcpnpx agentmods add agents/luanpdd/kit-mcp/detector-tenant-quenteWrote 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/detector-tenant-quente)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/detector-tenant-quente"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/detector-tenant-quente/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/detector-tenant-quente"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/detector-tenant-quente.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.00067 | $0.04063 |
| Opus 5 | $0.00034 | $0.02031 |
| Sonnet 5 | $0.00013 | $0.00813 |
| Haiku 4.5 | $0.00007 | $0.00406 |
Grade A, and why
detector-tenant-quente 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o detector-tenant-quente — agent da Suíte DDIA Foundations v1.22. Identifica outliers de uso por tenant em apps multi-tenant Supabase consultando logs reais via mcp__supabase__execute_sql, aplica thresholds canônicos (3× P50 = WARN, 10× P50 = CRITICAL) da skill tenant-quente-mitigacao, e produz AUDITORIA-TENANT-QUENTE.md com top 5 tenants quentes + 3 métricas + estratégia de mitigação sugerida.
Compat: Full em Claude Code + Cursor (com Supabase MCP). Partial em Codex + Gemini CLI; Offline-only fallback usa apenas heurísticas estáticas (tabelas grandes em migrations).
Por que existe
Em apps multi-tenant compartilhados (single-schema + org_id), 1 tenant pode gerar 80% das queries — distribuição power-law canônica. Sem detection ativa, isso causa:
- Cost overrun silencioso — Supabase Compute escala com query load, 1 tenant quente eleva custo de todos
- Noisy neighbor degradation — outros tenants veem latência maior nos mesmos shared resources
- Failure mode ampliado — quando tenant quente sofre incident, recovery é mais lento
DDIA Ch 6 (Partitioning) cataloga "skewed workloads" como problema canônico. Supabase + Postgres single-leader não particiona automaticamente — operador precisa identificar manualmente. Este agent automatiza essa detecção: scaneia pg_stat_statements, pg_total_relation_size, pg_stat_activity agrupado por org_id, aplica thresholds, e produz lista priorizada de mitigações.
Phase 122 (AGENTE-03..04) introduz este agent à Suíte DDIA Foundations v1.22. Pattern v1.21 herdado: agent detecta + sugere estratégia, mas NÃO aplica mitigação — delega via cross-suite handoff.
Inputs esperados (do caller)
- (Opcional)
project_id: identificador Supabase MCP — se ausente, modo offline-fallback - (Opcional)
output_path: default.planning/AUDITORIA-TENANT-QUENTE.md - (Opcional)
time_window: janela de logs a analisar (default:30 days) - (Opcional)
top_n: quantos tenants quentes incluir no relatório (default:5)
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 · 338 lines · 67 tokens per session scan A 60b8fcf0a9e6
detector-tenant-quente is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 4,063 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.
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…
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".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
sql-expert
Usa este agente para cualquier tarea relacionada con base de datos en FacturaScripts: diseñar esquemas de tabla XML, optimizar consultas con DbQuery y Where, crear índices y constraints, escribir migraciones SQL, analizar rendimiento de queries, usar transacciones, trabajar con DataBaseWhere/DataBase/DbQuery, diseñar…