sent-compliance

sent-compliance is a skill for Claude Code, Codex from sentdm/sent-plugin. It costs 87 tokens per session (675 once invoked), scanned B, original, MIT.

A tool guide for finding SMS sender compliance requirements and a setup plan for a country and phone-number type. SMS sender compliance means meeting local rules before sending business text messages.

In plain words
What is it for?
It is for checking market requirements and preparing an SMS sender setup plan; it does not register the sender itself.
Why use it?
It helps identify required registrations, documents, and fields before provisioning a sender, while distinguishing SMS from WhatsApp and RCS requirements.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the sent plugin — 21 skills, 1 MCP server shipped together

Good fit It is for checking market requirements and preparing an SMS sender setup plan; it does not register the sender itself.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sentdm/sent-plugin/sent-compliance
Install

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.

Any agent
npx skills add sentdm/sent-plugin --skill sent-compliance
Clone the repo
git clone --depth 1 https://github.com/sentdm/sent-plugin

Made for: Claude Code, Codex.

Or install sent, the plugin that ships this one along with the rest of its 21 skills, 1 MCP server.

Wrote 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.

agentmods badge for sent-compliance

README.md
[![agentmods](https://agentmods.dev/badge/skills/sentdm/sent-plugin/sent-compliance/github.svg)](https://agentmods.dev/skills/sentdm/sent-plugin/sent-compliance)
Your own site
<a href="https://agentmods.dev/skills/sentdm/sent-plugin/sent-compliance"><img src="https://agentmods.dev/badge/skills/sentdm/sent-plugin/sent-compliance/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.

agentmods 80×15 button for sent-compliance

Your own site · 80×15
<a href="https://agentmods.dev/skills/sentdm/sent-plugin/sent-compliance"><img src="https://agentmods.dev/badge/skills/sentdm/sent-plugin/sent-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 675 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00087 $0.00675
Opus 5.5 $0.00035 $0.00270
Sonnet 5.5 $0.00017 $0.00135
Haiku 4.5 $0.00009 $0.00068

Measured today against content hash a102d844b679, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

sent-compliance scanned grade B 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 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.

Subtle steeringmediumPrompt injection

Instructions that bias recommendations or shape behaviour without the user noticing.

2. Check `hasRegime` before interpreting an empty requirements list. An empty list with a published regime can mean no fields are demanded; `hasRegime: false` means no schema is published and is not proof that no complia
claude-plugins/sent/skills/sent-compliance/SKILL.md · 27 lines

How it starts

The opening of the file, as written. The whole thing — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sent Compliance

Use the read-only compliance.requirements and compliance.setup_plan tools before provisioning a dedicated SMS sender. They describe a market; they do not register a sender or mutate a profile.

Resolve the market

Use client-managed OAuth 2.1/PKCE and never request or expose credentials. Resolve country as an ISO 3166-1 alpha-2 code and type as LOCAL, MOBILE, TEN_DLC (or 10DLC), TOLL_FREE, SHORT_CODE, or ALPHANUMERIC. channel defaults to sms; only SMS is supported. Route WhatsApp to waba-embedded-signup and RCS to rcs-agent-onboarding rather than interpreting refusal as no requirements.

The optional profileId selector is available only for an organization's owned profile. Requirements are account-independent; it does not change the market's rules or make the plan target an existing profile.

Interpret requirements and plan

  1. Call compliance.requirements for the selected market. Preserve required flags, conditional rules, options, item fields, sender pattern, and attachment field names.
  2. Check hasRegime before interpreting an empty requirements list. An empty list with a published regime can mean no fields are demanded; hasRegime: false means no schema is published and is not proof that no compliance is required. US TOLL_FREE numbers require toll-free verification before production traffic, even when no requirements are returned; never tell the user that a toll-free number needs no registration.
  3. Call compliance.setup_plan when the user needs the setup steps for a market. From Claude, Sender Profiles are provisioned in the Sent Dashboard: present the plan's requirements, and when it returns a Dashboard handoff, give the user that link. If the plan contains a call that would create a Sender Profile, do not call sender_profiles.create; hand the setup to the Dashboard. Do not translate the plan into an invented REST call.
  4. If canCompleteHere is false, report blocker and attachments, then hand off document submission to the Sent dashboard or the documented multipart REST workflow. Required uploads cannot be carried through MCP. Optional attachment fields alone do not necessarily block creation.
  5. When setup can proceed, direct the user to finish provisioning in the Sent Dashboard with the requirements you gathered.

Read the full file on GitHub · 27 lines

Files

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.

Changes

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.

  1. today Changed scan A → B a102d844b679
  2. 17d ago First seen · 27 lines · 87 tokens per session scan A c27bd0247c29

Subscribe to this mod's changes

sent-compliance is a skill published in the GitHub repository sentdm/sent-plugin (51 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 675 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (subtle steering). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-03.

Related

Other skills, from other repositories

fto-triage

Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…

anthropics/claude-for-legal · 81 tokens

legal-hold

Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.

anthropics/claude-for-legal · 68 tokens

specification-writing

A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.

wanshuiyin/Auto-claude-code-research-in-sleep · 49 tokens

regulatory-research-fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs.

HKUDS/OpenSpace · 20 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens

memstack-business-gdpr

Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…

cwinvestments/memstack · 121 tokens