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 liguelead/mcp --skill skillgit clone --depth 1 https://github.com/liguelead/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/skills/liguelead/mcp/skill)<a href="https://agentmods.dev/skills/liguelead/mcp/skill"><img src="https://agentmods.dev/badge/skills/liguelead/mcp/skill/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/liguelead/mcp/skill"><img src="https://agentmods.dev/badge/skills/liguelead/mcp/skill.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.00083 | $0.03063 |
| Opus 5.5 | $0.00033 | $0.01225 |
| Sonnet 5.5 | $0.00017 | $0.00613 |
| Haiku 4.5 | $0.00008 | $0.00306 |
Grade A, and why
liguelead-api scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "https://api.liguelead.com.br/v1/voice/uploads" \ How it starts
The opening of the file, as written. The whole thing — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LigueLead API – Integration Skill
Overview
LigueLead is a Brazilian communications platform for voice, SMS, and RCS. This skill covers:
- Authentication via dual-header (
api-token+app-id) - Voice calls (2-step process: upload audio → send campaign)
- SMS (standard and Flash) in a single request
- RCS (template creation — text/media/card/carousel — then send)
- Webhooks for real-time campaign status
Base URL: https://api.liguelead.com.br/v1
1. Authentication
Every request requires two mandatory headers:
api-token: YOUR_API_TOKEN
app-id: YOUR_APP_ID
Content-Type: application/json
Where to get them: LigueLead Dashboard → Integrações → API Token (areadocliente.liguelead.app.br)
⚠️ Never expose
api-tokenorapp-idin client-side code. Use environment variables.
2. Phone number format
The API accepts three Brazilian phone number formats:
| Format | Example | Digits |
|---|---|---|
| National (recommended) | 11999999999 |
11 |
| International | +5511999999999 |
14 chars |
DDI without + |
5511999999999 |
13 |
Recommendation: use the national format (11 digits) for best compatibility.
3. Sending voice calls
Voice sending is a 2-step process.
Step 1 — Upload audio
POST /v1/voice/uploads — multipart/form-data
curl -X POST "https://api.liguelead.com.br/v1/voice/uploads" \
-H "api-token: YOUR_API_TOKEN" \
-H "app-id: YOUR_APP_ID" \
-F "title=My Message" \
-F "file=@/path/to/audio.mp3"
Response (201):
{
"message": "Voice upload successful.",
"data": {
"id": 436514,
"title": "My Message"
}
}
Save the
id— it's thevoice_upload_idfor the next step.
File limits:
- Supported formats: MP3 and WAV (AAC and M4A not supported)
- Max size: 50 MB (recommended: 5–10 MB)
- Storage per account: 10 GB | Max 1,000 active files
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 · 367 lines · 83 tokens per session scan A a1723d0dc874
liguelead-api is a skill published in the GitHub repository liguelead/mcp (1 stars, last pushed 14d ago), licensed MIT. It adds 83 tokens to every session and 3,063 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
apitap
ApiTap gives AI agents cheap access to web data through three layers.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.
frontmcp-setup
Use when starting, scaffolding, or organizing a FrontMCP project. Covers creating a new project (CLI scaffold or manual) for Node, Vercel, and other targets; standalone versus Nx-monorepo layout, naming conventions, generators, and dependency rules; composing multiple @App classes, ESM packages, and remote MCP servers…