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 skills add IAPro-Community/Orquestrador-Maestro --skill skill-whatsapp-meta-ads-leadsgit clone --depth 1 https://github.com/IAPro-Community/Orquestrador-MaestroWrote 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/skills/iapro-community/orquestrador-maestro/skill-whatsapp-meta-ads-leads)<a href="https://agentmods.dev/skills/iapro-community/orquestrador-maestro/skill-whatsapp-meta-ads-leads"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-whatsapp-meta-ads-leads/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/skills/iapro-community/orquestrador-maestro/skill-whatsapp-meta-ads-leads"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-whatsapp-meta-ads-leads.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.00861 |
| Opus 5 | $0.00016 | $0.00430 |
| Sonnet 5 | $0.00007 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
skill-whatsapp-meta-ads-leads 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Campanhas de WhatsApp para Leads no Meta Ads
Use esta skill para planejar campanhas, instrumentar aquisição e devolver sinais de qualidade de lead ao Meta. A interface e os nomes de objetivos podem mudar; confirme o fluxo disponível no Ads Manager da conta antes de publicar.
Estratégia
- Defina o resultado de negócio: conversa iniciada, lead capturado, lead qualificado ou venda.
- Escolha o objetivo e o local de conversão exibidos atualmente para a conta; não trate “Leads” como universalmente superior a “Engajamento” ou “Vendas”.
- Conecte um número do WhatsApp Business elegível e confirme permissões, horário de atendimento, responsáveis e política de opt-in.
- Use criativos, perguntas iniciais e segmentação local coerentes com o serviço real.
- Registre
campaign_id,adset_id,ad_id, UTMs, timestamp, consentimento e telefone normalizado no CRM.
Integração de API
- Para eventos de site ou CRM, prefira a Meta Conversions API pelo backend, com token e pixel/dataset ID fora do navegador.
- Envie somente eventos necessários, como
Lead, um evento interno de qualificação mapeado para o esquema aceito pela conta, ePurchasequando houver compra confirmada. - Use
event_idestável para deduplicar eventos enviados pelo Pixel e pela Conversions API. - Valide o consentimento e minimize PII; aplique hash somente conforme o formato exigido pela documentação da Meta e nunca faça hash de dados que não deveriam ser coletados.
- Fixe a versão da Graph/Marketing API no cliente do servidor e registre a data de revisão. Não copie uma versão encontrada em exemplo antigo.
- Ao usar WhatsApp Cloud API diretamente, trate webhook de mensagens, janela de atendimento, templates aprovados, limites e qualidade como contratos separados da campanha. Para Evolution API, encaminhe para
skill-evolution-api.
Operação e Métricas
| Métrica | Uso |
|---|---|
| CPL | Custo por lead capturado |
| Taxa de qualificação | Qualidade real do tráfego |
| Tempo de primeira resposta | Velocidade do atendimento |
| Conversão em venda | Resultado de negócio |
| ROAS | Retorno sobre mídia quando a receita é confiável |
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 · 66 lines · 33 tokens per session scan A f8e1b479ef5d
skill-whatsapp-meta-ads-leads is a skill published in the GitHub repository IAPro-Community/Orquestrador-Maestro (42 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 861 once invoked, about $0.0002 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 skills, from other repositories
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
dry-run
Preview command effects without making changes. Simulates file writes, git operations, agent spawns, and state changes. All reads execute normally for accurate preview. Use --dry-run flag on any command.
task-breakdown-phase
Standard Operating Procedure for /tasks phase. Covers task sizing, acceptance criteria definition, and TDD-first task sequencing. (project).
finalize-phase
Completes feature/epic workflows after deployment with comprehensive walkthrough generation for epics (v5.0+), roadmap updates, artifact archival, documentation, and branch cleanup. Use after /ship-prod, /deploy-prod, or /build-local completes, or when user asks to finalize. (project).
staging-deployment-phase
Deploys features to staging environment with database migrations, health checks, and deployment verification. Use during /ship-staging phase or when deploying to staging environments for validation before production release.
multi-agent-voting
Execute multi-agent voting for critical decisions using MAKER-style first-to-ahead-by-k error correction.