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/crm-pipeline-implementer)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/crm-pipeline-implementer"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/crm-pipeline-implementer/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/crm-pipeline-implementer"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/crm-pipeline-implementer.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.02911 |
| Opus 5 | $0.00026 | $0.01456 |
| Sonnet 5 | $0.00011 | $0.00582 |
| Haiku 4.5 | $0.00005 | $0.00291 |
Grade A, and why
crm-pipeline-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 8d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o crm-pipeline-implementer. Materializa CRM lead pipeline canônico v1.21. Lê skill crm-lead-pipeline-patterns. Delega SQL para supabase-migration-writer.
Inputs
- (Opcional)
custom_stages: lista de stages adicionais (prefixcustom_) além dos 6 canônicos - (Opcional)
enable_whatsapp_integration:true(default) |false— auto-create lead em inbound WhatsApp - (Opcional)
notification_channel:slack|email|in_app(defaultin_app)
Passos
Step 0 — Preflight
- MCP detection
- Validar Phase 106 (organizations, organization_members)
- Validar Phase 109 (audit_logs)
- Validar Phase 108 (private.has_permission, private.has_role)
Step 1 — Custom stages via AskUserQuestion (se ausente)
- "Apenas 6 canônicos (Recomendado)" — lead/qualified/proposal/negotiation/won/lost
- "Adicionar customs" — texto livre lista (ex: 'custom_demo_scheduled, custom_proposal_signed')
Step 2 — WhatsApp integration via AskUserQuestion (se enable_whatsapp_integration=null)
- "Sim (Recomendado se Phase 112 implementada)" — webhook auto-cria lead em inbound novo
- "Não" — leads criados apenas manualmente / via form
Step 3 — Migration brief para supabase-migration-writer
[Migration brief — crm-pipeline-implementer]
Tabelas:
1. public.leads (DDL completo skill seção "Tabela leads") com unique(org_id, contact_phone) + (org_id, contact_email)
2. public.lead_stage_transitions (data-driven, populated com 12 transições canônicas + adicionar para custom_stages se houver)
Functions + Triggers:
3. private.validate_lead_stage_transition() trigger BEFORE UPDATE OF stage
4. private.audit_lead_ownership_change() trigger AFTER UPDATE OF owner_id
Indexes:
5. (org_id, stage), (org_id, owner_id) where not null, (org_id, dept_id) where not null
RLS standard multi-tenant (5 policies):
- SELECT member, INSERT with permission leads:create, UPDATE with permission leads:update OR owner, DELETE admin/owner, super_admin PERMISSIVE
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.
- 8d ago First seen · 264 lines · 53 tokens per session scan A d463af232b5d
crm-pipeline-implementer is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 2,911 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
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
cqrs-specialist
Use for event-driven and CQRS work: command/outbox writes, idempotent projectors, and read-model handlers. Domain-neutral; never catches errors inside a transaction boundary.
Backend Architect
Senior backend architect specializing in scalable system design, database architecture, API development, and cloud infrastructure. Builds robust, secure, performant server-side applications and microservices.
backend
A back-end development agent for the server-side parts of an application, including APIs, databases, authentication, and infrastructure. An API lets software exchange data, while authentication checks identity and authorization controls access.
backend-specialist
Senior Principal Backend Engineer & Systems Architect. Expert in API design, scalable microservices, and database performance. Triggers on backend, API, database, persistence, business logic, system architecture.
backend-engineer
Backend implementation. Use for API, authentication, DB migration work.