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 sent-two-way-messaginggit 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-two-way-messaging)<a href="https://agentmods.dev/skills/sentdm/sent-plugin/sent-two-way-messaging"><img src="https://agentmods.dev/badge/skills/sentdm/sent-plugin/sent-two-way-messaging/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-two-way-messaging"><img src="https://agentmods.dev/badge/skills/sentdm/sent-plugin/sent-two-way-messaging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- 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.00090 | $0.01478 |
| Opus 5.5 | $0.00036 | $0.00591 |
| Sonnet 5.5 | $0.00018 | $0.00296 |
| Haiku 4.5 | $0.00009 | $0.00148 |
Grade A, and why
sent-two-way-messaging 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 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.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sent Two-Way Messaging
Inbound messaging on Sent has one governing rule: consent is enforced by the platform before the application sees the event. An inbound STOP has already flipped the contact's opt_out flag by the time message.received arrives. The application's job is to record it, reflect it in its own UI, and never attempt to send around it.
Keyword handling
Ten keywords ship as defaults:
| Action | Keywords |
|---|---|
| Opt out | STOP, CANCEL, UNSUBSCRIBE, QUIT, END |
| Opt in | START, UNSTOP, SUBSCRIBE |
| Help auto-reply | HELP, INFO |
Matching requires the entire trimmed message body to equal a keyword, case-insensitively. "Please stop messaging me" does not match; "stop" does. Custom keywords are configured in the Sent Dashboard under Compliance, Opt Keywords, with an action of Opt Out, Opt In, or Help, and each must be a single exact token.
Do not claim keywords that are not in the documented set. In application code, mirror the same exact-match rule only to update local subscriber state and audit evidence; never use that matcher to apply consent to Sent a second time. Keep custom dashboard keywords synchronized with the local mirror, and reconcile against the contact's opt_out field when uncertain.
Consent state
An opt-out sets opt_out on the contact record. Consent is contact-level and channel-agnostic: a STOP sent over SMS suppresses WhatsApp and RCS for that contact as well. Consent gates re-apply on every reroute attempt, not only at initial send.
Restoring consent requires the recipient's own action. A user-initiated opt-in keyword clears suppression. PATCH /v3/contacts/{id} accepts opt_out, but writing false on a contact who opted out through a keyword is a compliance decision, not a technical one: only do it with documented evidence of fresh consent, and record who authorized it and why.
Downstream, a suppressed send does not fail with an error. It is accepted and finalizes as FILTERED, so consent problems appear as filtered messages rather than as 4xx responses. Details are in references/consent-and-keywords.md.
What ships with it
4 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.
- 1mo ago First seen · 76 lines · 90 tokens per session scan A e0dbccbcced4
sent-two-way-messaging is a skill published in the GitHub repository sentdm/sent-plugin (51 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 1,478 once invoked, about $0.0004 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-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.
waniwani-sdk
MCP distribution SDK: build sales funnels, lead generation, booking flows, insurance quote flows, pricing quote flows, and any multi-step conversational MCP app with @waniwani/sdk. Open source createFlow engine (no API key required) with pluggable state backends (in-memory, Redis, Upstash, Cloudflare KV, DynamoDB, or…
migrate-waniwani-sdk-0.22-to-0.23
Migrate a project from @waniwani/sdk 0.22.x to 0.23.x and auto-apply its breaking change: withWaniwani's captureTelemetry option and the CaptureTelemetryOptions type are removed in favour of captureIntent / CaptureIntentOptions, and every wrapped tool advertises one optional intent string instead of the nested…
scaffold-ai-app
Scaffold a Veryfront app with AI tools, agent definitions, and knowledge base.
trtc
Use for TRTC/Tencent RTC requests to integrate, build, troubleshoot, compare, price, migrate, or query SDK/API/docs. Also trigger when the request omits “TRTC” but concerns audio/video, chat, calls, meetings, live, voice rooms, offline push, or AI. Route by product/platform/intent. Products: Chat/IM/TUIKit…
trtc-conference
A guided workflow for building a TRTC Conference web application step by step. TRTC Conference provides real-time group video and voice communication in a web app.