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 sender-profile-architectgit 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/sender-profile-architect)<a href="https://agentmods.dev/skills/sentdm/sent-plugin/sender-profile-architect"><img src="https://agentmods.dev/badge/skills/sentdm/sent-plugin/sender-profile-architect/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/sender-profile-architect"><img src="https://agentmods.dev/badge/skills/sentdm/sent-plugin/sender-profile-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 72 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00060 | $0.01486 |
| Opus 5.5 | $0.00024 | $0.00594 |
| Sonnet 5.5 | $0.00012 | $0.00297 |
| Haiku 4.5 | $0.00006 | $0.00149 |
Grade A, and why
sender-profile-architect 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 17d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sender Profile Architect
A Sender Profile is the operational boundary for tenant identity, channel configuration, inherited resources, billing, and credentials. Use this skill before provisioning when a poor boundary would mix brands, compliance posture, rate-limit impact, or webhook ownership.
For live MCP profile lifecycle operations use sent-profile-provisioning; for market requirements use sent-compliance. MCP selects an acting profile with optional profileId on ordinary account tools for organization grants only. sender_profiles.* tools operate on target id and reject acting profileId. REST headers below are not MCP arguments.
Recommended tenancy model
When tenants require isolation, recommend one Sent organization with one Sender Profile per tenant. A shared profile is appropriate only when the tenants genuinely share one brand, sender resources, compliance posture, billing/rate-limit expectations, and operational blast radius.
Do not recommend pooled-by-default architecture. Make the isolation decision explicit using references/multi-tenancy-patterns.md.
Authentication patterns
Sent v3 supports both:
| Pattern | Headers | Blast radius |
|---|---|---|
| Profile-specific API key | x-api-key |
Profile-scoped credentials and rate-limit context. Do not add x-profile-id. |
| Organization API key acting for a child | x-api-key plus x-profile-id: <profile UUID> |
Organization credential can reach permitted child profiles; rate limits remain in the organization pool. |
Only organization keys may send x-profile-id. A profile key that sends it receives 403. A profile outside the organization returns 404. X-Profile-Id can be echoed in scoped responses.
x-sender-id is legacy v1/v2 terminology only. Do not use it for v3 authentication or routing.
Choose profile keys when tenant-level credential isolation and revocation are primary. Choose organization-key scoping for centrally controlled integrations that can protect a broader credential and deliberately accept a shared organization rate-limit pool.
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.
- 17d ago Changed · +2 lines 96d218927a8b
- 1mo ago First seen · 122 lines · 60 tokens per session scan A 1d0f0e09205a
sender-profile-architect is a skill published in the GitHub repository sentdm/sent-plugin (51 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 1,486 once invoked, about $0.0002 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.