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/audit-log-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/audit-log-implementer)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/audit-log-implementer"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/audit-log-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.00058 | $0.03613 |
| Opus 5 | $0.00029 | $0.01806 |
| Sonnet 5 | $0.00012 | $0.00723 |
| Haiku 4.5 | $0.00006 | $0.00361 |
Grade A, and why
audit-log-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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o audit-log-implementer. Materializa o audit log canônico v1.21 — tabela append-only + helper function + retention scheduler. Delega SQL final para supabase-migration-writer (cross-suite). Lê skill audit-log-multi-tenant como base.
Compat: Full em Claude Code + Cursor (com Supabase MCP); Partial em Codex + Gemini CLI.
Por que existe
Audit log é pré-requisito BLOCKER para Phase 111 (super-admin) — sem ele, super_admin opera sem rastro. Este agent garante que o pattern canônico (append-only + PII sanitization + retention multi-tier + legal_hold) seja materializado consistentemente, sem improviso por phase.
Inputs esperados (do caller)
- (Opcional)
default_tier:free(30d) |pro(90d) |enterprise(365d) — se ausente, usafreecomo default + aplica per-org viaorganizations.plan - (Opcional)
partitioning:true|false— true só se app espera >50k events/org/ano. Defaultfalse(single table) - (Opcional)
extra_event_types: lista de custom event types (prefixcustom_) além dos 7 canônicos - (Opcional)
audit_super_admin_tables: lista de tabelas que ganham trigger automático de audit super_admin
Passos
Step 0 — Preflight
Detectar MCP. Verificar se Phase 106 schema existe (organizations, organization_members).
select exists (select 1 from information_schema.tables where table_schema = 'public' and table_name = 'organizations') as ok;
Se não existe → ABORT: "Phase 106 não implementada — schema base faltando."
Step 1 — Validar pg_cron extension
select extname from pg_extension where extname = 'pg_cron';
Se não habilitada:
⚠ pg_cron extension não habilitada — retention scheduler não vai funcionar.
Solução: na Supabase Dashboard → Database → Extensions → enable pg_cron.
Continuar mesmo assim? [yes/no]
Step 2 — Coletar tier preferences via AskUserQuestion (se default_tier ausente)
- "Free 30d (Recomendado para start)" — Org plan 'free' → 30 dias retention
- "Pro 90d" — Org plan 'pro' → 90 dias retention
- "Enterprise 365d" — Org plan 'enterprise' → 365 dias retention
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 · 323 lines · 58 tokens per session scan A b53d1ca282b7
audit-log-implementer is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 3d ago), licensed MIT. It adds 58 tokens to every session and 3,613 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.