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/evolution-go-integrator)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/evolution-go-integrator"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/evolution-go-integrator/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/evolution-go-integrator"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/evolution-go-integrator.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.00053 | $0.02465 |
| Opus 5.5 | $0.00021 | $0.00986 |
| Sonnet 5.5 | $0.00011 | $0.00493 |
| Haiku 4.5 | $0.00005 | $0.00247 |
Grade A, and why
evolution-go-integrator 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 1mo 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o evolution-go-integrator. Materializa integração completa WhatsApp em B2B multi-tenant — tabelas org_whatsapp_configs + whatsapp_messages, webhook handler Edge Function, send queue + worker. Lê skills evolution-go-whatsapp-integration + whatsapp-conversation-state-machine. Delega Edge Function code para supabase-edge-fn-writer.
Inputs
- (Opcional)
provider:meta_cloud(Meta Cloud API oficial) |evolution_go(whatsmeow não-oficial) - (Opcional)
enable_send_queue:true(default — pgmq + worker) |false(sync send, sem rate limit guard) - (Opcional)
enable_state_machine:true(default — xstate conversation) |false(só persist messages, sem state)
Passos
Step 0 — Preflight
- MCP detection
- Validar Phase 106 (organizations, organization_members)
- Validar Phase 109 (audit_logs + audit_log function)
- Validar pgmq extension habilitada (se enable_send_queue=true)
- ABORT se HMAC validation aplicada APÓS JSON.parse — REGRA #1 da skill (este check é pre-design, agent reforça no brief)
Step 1 — Provider via AskUserQuestion (se ausente)
- Meta Cloud API (Recomendado para production) — oficial Meta, custo por conversation, rate limit 80 msg/s, HMAC-SHA256 signature
- Evolution Go (free/self-hosted) — whatsmeow library, sem custo Meta, throttle manual 1 msg/s, API key + IP whitelist (não HMAC)
- Ambos (multi-provider) — cada org escolhe via org_whatsapp_configs.provider
Step 2 — Migration brief para supabase-migration-writer
[Migration brief — evolution-go-integrator]
Tabelas:
1. public.org_whatsapp_configs (DDL completo skill section "Tabela org_whatsapp_configs")
2. public.whatsapp_messages (DDL completo com unique(org_id, message_id) — REGRA #4 idempotency)
3. (se enable_state_machine=true) public.conversations (DDL skill conversation-state-machine)
4. (se enable_send_queue=true) pgmq queue creation: select pgmq.create('whatsapp_outbound_global');
RLS standard multi-tenant para todas (members + super_admin bypass).
(se enable_send_queue=true) pg_cron worker schedule:
select cron.schedule('whatsapp-send-worker', '* * * * *', $$ select net.http_post(...) $$);
-- worker chama Edge Function whatsapp-send-worker que processa N msgs respeitando 80 msg/s
(se enable_state_machine=true) pg_cron timeout 24h:
select cron.schedule('conversation-timeout-24h', '*/30 * * * *', $$
update public.conversations set state = 'abandoned'
where state = 'waiting_user_reply' and last_message_at < now() - interval '24 hours';
$$);
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.
- 1mo ago First seen · 208 lines · 53 tokens per session scan A f557d82b8e7c
evolution-go-integrator is an agent published in the GitHub repository luanpdd/kit-mcp (4 stars, last pushed 6d ago), licensed MIT. It adds 53 tokens to every session and 2,465 once invoked, about $0.0002 per session on Opus 5.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
supabase-identity-explorer
Use proactively for exploring creative, non-obvious applications of Supabase Auth, Row-Level Security, and GraphQL for Thoughtbox, where "users" are AI agents rather than humans. Specialist for generating surprising identity-dimension design proposals grounded in metaphors of theatrical masks, legal personhood, and…
backend-platform-engineer
Builds and reviews backend services — NestJS modules, APIs, Postgres access, Redis/BullMQ workers, async workflows. Use for implementation, code, tests, debugging and refactoring. Escalates architecture-level decisions to principal-engineer.
backend-engineer
Backend implementation. Use for API, authentication, DB migration work.
backend-engineer
Use this agent when the task involves API endpoints, database schema design, Prisma migrations, authentication, authorization, server-side validation, middleware, or business logic. For example: creating a new REST endpoint with request validation, adding a Prisma model and migration, implementing JWT auth with…
backend
Go backend specialist. OpenAPI-first, Echo handlers, Firestore, Cloud Run. Use for backend features, API design.
backend-dev
An agent for building and fixing server-side software, including APIs, business rules, databases, background jobs, authentication, and caching.