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 Kanzando/Mcp-Wacta --skill wactagit clone --depth 1 https://github.com/Kanzando/Mcp-WactaWrote 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/kanzando/mcp-wacta/wacta)<a href="https://agentmods.dev/skills/kanzando/mcp-wacta/wacta"><img src="https://agentmods.dev/badge/skills/kanzando/mcp-wacta/wacta.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.1 | $0.00103 | $0.01015 |
| Opus 5 | $0.00051 | $0.00508 |
| Sonnet 5 | $0.00021 | $0.00203 |
| Haiku 4.5 | $0.00010 | $0.00102 |
Grade A, and why
wacta 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 7d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operar WaCta por MCP
Herramientas disponibles (servidor wacta): wacta_status, wacta_get_settings, wacta_update_settings, wacta_list_ctas, wacta_save_cta, wacta_delete_cta, wacta_analytics_dashboard, wacta_analytics_ctas, wacta_studio_numbers.
Doctrina (siempre)
- Lee antes de escribir. Primer paso de cualquier tarea:
wacta_status(complementos activos, CTAs, tope del plan). Antes de cambiar ajustes de un plugin:wacta_get_settingsde ese plugin. - PATCH mínimo.
wacta_update_settingscambia SOLO las claves enviadas. Nunca reenvíes el objeto completo; envía exactamente lo que cambia. - Verifica con la respuesta. Toda escritura devuelve el estado final YA SANEADO. Compáralo con lo que enviaste: si difiere, el sanitizador acotó el valor — repórtalo, no reintentes a ciegas.
- Confirmación humana antes de tocar interruptores con impacto público:
activated(core),tracking_enabled/consent_enabled(analytics),frontend_enabled/portal_enabled(crm),externalMode:"managed"(studio, reescribe botones del sitio), y antes de borrar CTAs con actividad. En URLs que parezcan producción, confirma SIEMPRE. - El slug es identidad.
wacta_list_ctasantes de crear; jamás renombres un slug con historial (parte las métricas). El errorwacta_cta_limit= plan gratuito al tope (3): explícalo, no reintentes.
Recetas
Diagnóstico inicial — wacta_status → si falta un dato, wacta_get_settings del plugin. Resume: qué está encendido, número configurado, CTAs y tope.
Encender/configurar el widget — confirma número y mensaje con la persona; luego:
wacta_update_settings {plugin:"core", changes:{activated:true, dialCode:"52", localNumber:"5512345678", defaultMessage:"…"}}.
Hacer medible un botón existente (adopción) — la vía recomendada para "gobierna/mide este botón del tema":
wacta_save_cta {cta:{slug:"promo-hero", label:"Promo Hero", selector:".hero .btn-wa", message:"Quiero la promo de {titulo}", track:true}}.
Con capture:true el clic pide datos antes de abrir WhatsApp (fuerza el runtime base del core en esas páginas — adviértelo).
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.
- 7d ago First seen · 40 lines · 103 tokens per session scan A 08f1ecdfaf10
wacta is a skill published in the GitHub repository Kanzando/Mcp-Wacta (0 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 1,015 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…