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.
/plugin marketplace add sentdm/sent-pluginnpx agentmods add plugins/sentdm/sent-plugin/sentgit clone --depth 1 https://github.com/sentdm/sent-pluginGrade 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 2d 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.
What it actually says
{
"name": "sent",
"version": "0.1.0",
"description": "Official Sent business messaging plugin for SMS, WhatsApp, RCS, API integration, webhooks, routing, two-way messaging, Sender Profiles, migration, compliance, analytics, and agent-safe operations.",
"author": {
"name": "Sent",
"url": "https://sent.dm"
},
"homepage": "https://github.com/sentdm/sent-plugin#readme",
"repository": "https://github.com/sentdm/sent-plugin",
"license": "MIT",
"keywords": [
"sent",
"agent-skills",
"business-messaging",
"messaging",
"sms",
"whatsapp",
"rcs",
"10dlc",
"a2p",
"tcr",
"waba",
"rbm",
"contacts",
"templates",
"analytics",
"deliverability",
"sender-profiles",
"api-integration",
"webhooks",
"routing",
"two-way-messaging",
"migration",
"mcp"
],
"commands": "./.claude/commands",
"skills": "./skills",
"mcpServers": "./.mcp.json"
}
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.
- 2d ago First seen · 41 lines scan A 46252bdb6df0
sent is a plugin published in the GitHub repository sentdm/sent-plugin (52 stars, last pushed 22d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.