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/jondoescoding/jondoescoding-coding-rulesWrote 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/jondoescoding/jondoescoding-coding-rules/resend_implementation)<a href="https://agentmods.dev/rules/jondoescoding/jondoescoding-coding-rules/resend_implementation"><img src="https://agentmods.dev/badge/rules/jondoescoding/jondoescoding-coding-rules/resend_implementation/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/jondoescoding/jondoescoding-coding-rules/resend_implementation"><img src="https://agentmods.dev/badge/rules/jondoescoding/jondoescoding-coding-rules/resend_implementation.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.00018 | $0.06030 |
| Opus 5.5 | $0.00007 | $0.02412 |
| Sonnet 5.5 | $0.00004 | $0.01206 |
| Haiku 4.5 | $0.00002 | $0.00603 |
Grade A, and why
resend_implementation 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 — 849 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resend Email Implementation Guide
This rule provides a comprehensive guide for implementing Resend email functionality in any system, designed for developers at all levels.
🚀 SETUP: Integration Questions for AI Assistant
Before implementing Resend email functionality, the AI assistant should ask these key questions to ensure seamless integration:
📋 Required Information Checklist
Ask the user these questions in order:
-
"What type of application are you integrating Resend into?"
- FastAPI/Django/Flask web application
- Node.js/Express application
- Standalone Python script
- Other framework (specify)
-
"What domain will you be sending emails from?"
- Do you own a custom domain? (e.g., yourcompany.com)
- What email address should be the sender? (e.g., [email protected])
- Have you verified this domain in Resend dashboard yet?
-
"What types of emails will you be sending?"
- Alert/notification emails
- Welcome/onboarding emails
- Password reset emails
- Marketing emails
- System status updates
-
"Who should receive these emails?"
- Admin email addresses for alerts
- User email addresses from database
- Fixed list of recipients
- Dynamic recipient lists
-
"Do you have a Resend account and API key?"
- Have you signed up at resend.com?
- Do you have your API key ready?
- Where will you store the API key? (.env file, config service, etc.)
-
"What's your current project structure?"
- Where should email service files be created?
- Do you have existing configuration/settings files?
- Are you using environment variables already?
-
"What level of email customization do you need?"
- Simple text emails
- HTML templates with styling
- Dynamic content (user names, data, etc.)
- Multiple email templates
🎯 AI Assistant Implementation Strategy
Based on user answers, the AI should:
- Customize code examples to match their framework (FastAPI, Django, etc.)
- Adapt file paths to their project structure
- Configure domain settings based on their verified domain
- Create appropriate templates for their email types
- Set up environment variables matching their configuration style
- Provide testing scripts tailored to their use case
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 · 849 lines · 18 tokens per session scan A a85c8fa8f2fa
resend_implementation is a cursor rule published in the GitHub repository jondoescoding/jondoescoding-coding-rules (2 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 6,030 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
handler-patterns
Backend handler/controller pattern rules and flow. Apply when editing handlers or API routes.
code-organization
Backend code organization and structure rules. Apply when organizing backend source.
api-design
REST API design conventions and standards. Apply when designing or editing API endpoints.
error-handling
Error handling patterns for backend services. Apply when handling errors in handlers or services.
serverless
Serverless architecture patterns and Lambda/function best practices.
state-management
Frontend state management patterns and best practices. Apply when managing client state.