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 agentmods add skills/rahmanef63/si-coder-agent/sc-resendnpx skills add rahmanef63/si-coder-agent --skill sc-resendgit clone --depth 1 https://github.com/rahmanef63/si-coder-agentWrote 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/rahmanef63/si-coder-agent/sc-resend)<a href="https://agentmods.dev/skills/rahmanef63/si-coder-agent/sc-resend"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-resend.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00061 | $0.00725 |
| Opus 5 | $0.00030 | $0.00362 |
| Sonnet 5 | $0.00012 | $0.00145 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
sc-resend 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc-resend — Resend (STUB)
Status: boilerplate only.
Scope when implemented
- Domain verification: register a sending domain with Resend, fetch the DKIM/SPF/DMARC records it requires, then create them via
sc-cforlib/hostinger.jsautomatically — no manual DNS copy-paste. - API key rotation per project, scoped to the verified domain.
- Audience creation for broadcast lists (optional).
- Smoke send to a verified recipient to confirm DNS propagation.
Sender identity policy
Sender identity is project configuration, not repository-global policy. Use one explicitly verified Resend domain/account selected by the user and keep the visible project name separate from the sender address:
From: <Project Name> <[email protected]>
Reply-To: <optional monitored mailbox>
Do not infer a sender address from the application hostname. A project hosted at
app.example.com may legitimately send from a different verified domain. Keep the
project-local contract explicit:
[email protected]
EMAIL_PROJECT_NAME=<Project Name>
EMAIL_PROJECT_TAG=<project-slug>
EMAIL_REPLY_TO=
Framework adapters may map these values into native variables, but the selected project configuration remains the source of truth. Never bake another project's domain, sender, or display name into this skill.
Env vars
| Var | Purpose |
|---|---|
RESEND_API_KEY |
re_... server key |
RESEND_FROM_DOMAIN |
The verified sending domain |
Suggested file layout
sc-resend/
├── SKILL.md
└── scripts/
├── verify-domain.js # register + auto-create DNS records via sc-cf / hostinger
├── api-key.js # create/rotate scoped API key
├── audiences.js # CRUD audience (optional)
└── smoke-send.js # send a test email to confirm
Implementation notes
- API base:
https://api.resend.com - Auth:
Authorization: Bearer <RESEND_API_KEY> - Domain verify response gives 3 records
[{ name, type, value }]— feed those into the DNS module viaconfigureDns(). - DMARC: Resend recommends
v=DMARC1; p=none;initially, tighten top=quarantineonce SPF/DKIM are confirmed in DNS for 24h.
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.
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 · +33 lines d6e0e8034fb8
- 5d ago First seen · 42 lines · 61 tokens per session scan A 3f173dff11bc
sc-resend is a skill published in the GitHub repository rahmanef63/si-coder-agent (14 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 725 once invoked, about $0.0003 per session on Opus 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
convex-http-actions
External API integration and webhook handling including HTTP endpoint routing, request/response handling, authentication, CORS configuration, and webhook signature validation.
convex-migrations
Schema migration strategies for evolving applications including adding new fields, backfilling data, removing deprecated fields, index migrations, and zero-downtime migration patterns.
convex-agents
Building AI agents with the Convex Agent component including thread management, tool integration, streaming responses, RAG patterns, and workflow orchestration.
convex-cron-jobs
Scheduled function patterns for background tasks including interval scheduling, cron expressions, job monitoring, retry strategies, and best practices for long-running tasks.
convex-realtime
Patterns for building reactive apps including subscription management, optimistic updates, cache behavior, and paginated queries with cursor-based loading.
convex-security-audit
Deep security review patterns for authorization logic, data access boundaries, action isolation, rate limiting, and protecting sensitive operations.