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 sentdm/sent-plugin --skill sentgit clone --depth 1 https://github.com/sentdm/sent-pluginWrote 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/sentdm/sent-plugin/sent)<a href="https://agentmods.dev/skills/sentdm/sent-plugin/sent"><img src="https://agentmods.dev/badge/skills/sentdm/sent-plugin/sent/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/sentdm/sent-plugin/sent"><img src="https://agentmods.dev/badge/skills/sentdm/sent-plugin/sent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00067 | $0.01607 |
| Opus 5.5 | $0.00027 | $0.00643 |
| Sonnet 5.5 | $0.00013 | $0.00321 |
| Haiku 4.5 | $0.00007 | $0.00161 |
Grade A, and why
sent 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 today.
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sent Meta Dispatcher
Overview
This skill is a router, not a worker. When a request does not identify one clear Sent workflow, inspect the intent, ask only the clarification needed to select a route, and invoke the matching skill.
Sent spans direct account operations through its MCP server and specialist guidance for SMS, WhatsApp, RCS, Sender Profiles, templates, and delivery analysis. Prefer a direct-operation skill for live Sent data or mutations and a specialist skill for planning, compliance, diagnosis, or product design.
When to Use
Use when:
- The user mentions "Sent" broadly without naming a channel ("help me with Sent", "I want to use Sent for messaging")
- The user asks an open-ended question like "what can you help with on Sent?" or "where do I start?"
- The request could plausibly span multiple target skills (e.g., "messaging isn't working" — could be account readiness, 10DLC vetting, WABA template rejection, RBM capability, or an MDR funnel)
- The channel is ambiguous (SMS vs WhatsApp vs RCS not stated; geography matters because 10DLC is US-only)
- The surface is ambiguous (API integration vs dashboard UX vs compliance paperwork)
- The user pastes a Sent dashboard URL or API path without further context
Do not use when:
- The user has already named one supported operation or specialist workflow; invoke that skill directly.
- The question is purely about pricing, contracts, or unsupported product policy; point the user to
https://docs.sent.dmor Sent support.
Routing rules
MCP-backed operations
| User intent | Target skill |
|---|---|
| Preview, send, or schedule an existing templated message; inspect one message and its activity | sent-messaging |
| List, inspect, create, summarize, or delete Sent contacts | sent-contacts |
| Find, inspect, or delete existing Sent templates | sent-templates |
| Query dashboard messaging metrics or look up number capabilities | sent-analytics |
| Check the selected account, balance, onboarding state, or readiness to send | sent-account-readiness |
| Report a bug, missing feature, confusing result, or praise to Sent with user authorization | sent-feedback |
| Inspect SMS market fields, document requirements, or an exact setup call | sent-compliance |
| List, get, or update owned Sender Profiles through MCP, or hand creation and deletion to the Sent Dashboard | sent-profile-provisioning |
What ships with it
2 files 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.
- today Changed c23fe3fe0f27
- 17d ago Changed · +3 lines 2425d6da400d
- 1mo ago First seen · 94 lines · 67 tokens per session scan A 41261cf428e4
sent is a skill published in the GitHub repository sentdm/sent-plugin (51 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 1,607 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
eddi-screens
How an EDDI Manager page is actually built — the app shell, the list-page pattern, detail pages, the config-editor chrome, wizards, and loading/empty/error states. Load before creating or restructuring a page.
eddi-ui
EDDI Manager's UI vocabulary — the existing primitives and shared components, their variant props, the brand tokens, and the styling rules. Load before writing or editing any component that renders.
eddi-data
EDDI Manager's data and plumbing conventions — routing, TanStack Query hooks, ApiClient, i18n propagation, MSW mocks and tests. Load when wiring a screen to real data or adding a route.
chatbot
Use when a support or sales bot on a live website must behave: persona/system prompt, grounding so it cannot invent prices or policy, jailbreak and injection defense, the human handoff, launch metrics and kill switch. NOT the agent loop or RAG index under it (that is building-agents), NOT a human answering one ticket…
connector-setup
Use when the user wants to add, connect, sign in to or fix an MCP connector (a server that gives you tools for an app such as GitHub, Linear or Notion).
research
Use when the user asks you to research, compare, fact-check or find current information, and the answer should come with sources.