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.
git clone --depth 1 https://github.com/eliornl/rolemuleWrote 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/rules/eliornl/rolemule/email-and-misc-utils)<a href="https://agentmods.dev/rules/eliornl/rolemule/email-and-misc-utils"><img src="https://agentmods.dev/badge/rules/eliornl/rolemule/email-and-misc-utils/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/rules/eliornl/rolemule/email-and-misc-utils"><img src="https://agentmods.dev/badge/rules/eliornl/rolemule/email-and-misc-utils.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01994 |
| Opus 5.5 | $0.00000 | $0.00798 |
| Sonnet 5.5 | $0.00000 | $0.00399 |
| Haiku 4.5 | $0.00000 | $0.00199 |
Grade A, and why
email-and-misc-utils 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email, Resume Parser & Encryption Utilities
Email Service (Gmail SMTP)
from utils.email_service import EmailService
email_service = EmailService()
await email_service.send_password_reset_email(
to_email="[email protected]",
reset_token="token",
reset_url="https://app.example.com/auth/reset-password?token=xxx",
)
await email_service.send_verification_email(
to_email="[email protected]",
verification_token="token",
verification_url="https://app.example.com/auth/verify-email?token=xxx",
)
await email_service.send_welcome_email(to_email="[email protected]", user_name="Jane Doe")
When to Send the Welcome Email
- Email/password registration: sent after successful
POST /auth/verify-code(not at registration time, so unverified users don't get it). - Google OAuth new user: sent immediately inside the OAuth callback after the new user record is committed — Google has already verified the email. Existing Google users logging in again do not get a second welcome email.
Email Design Standards (all three transactional emails must match)
All three emails — welcome, password reset, and verification code — share the same structural and visual template:
| Property | Value |
|---|---|
| Outer container max-width | 580px |
Card border-radius |
20px |
| Header corner radius | 20px 20px 0 0 |
| Footer corner radius | 0 0 20px 20px |
Title (h1) font size |
28px |
| Subtitle text | "One mule for every role." |
Greeting (h2) font size |
22px, font-weight: 600 |
| Page background | #0d1117 |
| Card background | #161b22 |
| Accent gradient | linear-gradient(135deg, #00d4ff 0%, #7c3aed 100%) |
Never deviate from these values when editing a single email — update all three together to keep them consistent.
Absolute URLs in Email Templates — Always Use settings.base_url
Email clients (Gmail, Outlook, etc.) do not resolve relative URLs. Every link or button inside an email must be an absolute URL built from self.settings.base_url:
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 · 194 lines · 0 tokens per session scan A 0c90cfbbbc9f
email-and-misc-utils is a cursor rule published in the GitHub repository eliornl/rolemule (38 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,994 tokens. 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 cursor rules, from other repositories
development
Development environment setup and commands for backend services.
provider
The provider package defines the core interfaces and base classes that all AI providers must implement. It provides a unified abstraction layer for different AI services.
skill-mcp-server
Padrões DARE para servidores MCP (Model Context Protocol da Anthropic) em TypeScript ou Python. Tools, resources, prompts; transports stdio/SSE/HTTP; validação Zod/Pydantic; autorização por tool; observabilidade; testes; publicação.
skill-nestjs-api
Padrões DARE para APIs REST em NestJS + TypeScript + Prisma + Swagger. Modules, Controllers, Services, DTOs com class-validator, Guards JWT, throttler, exceções globais, Jest + Supertest, OpenAPI auto-gerado.
skill-laravel-api
Padrões Globais para Projetos Laravel API (Context Engineering).
backend-python
Python and FastAPI standards for the backend.