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 agentmods add skills/sendchamp/ai/sendchamp-sms-send-messagenpx skills add sendchamp/ai --skill sendchamp-sms-send-messagegit clone --depth 1 https://github.com/sendchamp/aiWrote 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/sendchamp/ai/sendchamp-sms-send-message)<a href="https://agentmods.dev/skills/sendchamp/ai/sendchamp-sms-send-message"><img src="https://agentmods.dev/badge/skills/sendchamp/ai/sendchamp-sms-send-message.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 | $0.00075 | $0.01168 |
| Opus 5 | $0.00037 | $0.00584 |
| Sonnet 5 | $0.00015 | $0.00234 |
| Haiku 4.5 | $0.00007 | $0.00117 |
Grade B, and why
sendchamp-sms-send-message scanned grade B with 2 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 4d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
resp = requests.post( "https://api.sendchamp.com/api/v1/sms/send", Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**curl** How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sendchamp SMS — Send Message
Overview
Sendchamp SMS API delivers transactional and promotional SMS across Africa. Unlike global providers, Sendchamp encodes Nigerian DND routing directly — critical for OTP and marketing compliance.
| Use case | Recommended route |
|---|---|
| OTP, alerts, order updates | non_dnd |
| Nigerian marketing/promo | dnd |
| International recipients | international |
Prerequisites
- Sendchamp account with funded wallet — my.sendchamp.com/signup
- Approved sender ID registered in dashboard
- Environment variable:
SENDCHAMP_ACCESS_KEY
export SENDCHAMP_ACCESS_KEY=sendchamp_live_YOUR_KEY
Quickstart
curl
curl -X POST https://api.sendchamp.com/api/v1/sms/send \
-H "Authorization: Bearer $SENDCHAMP_ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "+2348012345678",
"message": "Your order #1234 has shipped.",
"sender_name": "MyBrand",
"route": "non_dnd",
"country_code": "NG"
}'
Node.js
const res = await fetch("https://api.sendchamp.com/api/v1/sms/send", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.SENDCHAMP_ACCESS_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
to: "+2348012345678",
message: "Your order #1234 has shipped.",
sender_name: "MyBrand",
route: "non_dnd",
country_code: "NG",
}),
});
const data = await res.json();
Python
import os, requests
resp = requests.post(
"https://api.sendchamp.com/api/v1/sms/send",
headers={
"Authorization": f"Bearer {os.environ['SENDCHAMP_ACCESS_KEY']}",
"Content-Type": "application/json",
},
json={
"to": "+2348012345678",
"message": "Your order #1234 has shipped.",
"sender_name": "MyBrand",
"route": "non_dnd",
"country_code": "NG",
},
)
Key patterns
Multiple recipients
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 160 lines · 75 tokens per session scan B d0ed2f922521
sendchamp-sms-send-message is a skill published in the GitHub repository sendchamp/ai (0 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 1,168 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, 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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…