Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/agents/eddiebelaval/squire/email-notification-specialist)<a href="https://agentmods.dev/agents/eddiebelaval/squire/email-notification-specialist"><img src="https://agentmods.dev/badge/agents/eddiebelaval/squire/email-notification-specialist.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.1 | $0.00009 | $0.02004 |
| Opus 5 | $0.00005 | $0.01002 |
| Sonnet 5 | $0.00002 | $0.00401 |
| Haiku 4.5 | $0.00001 | $0.00200 |
Grade A, and why
email-notification-specialist 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 8d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Notification Specialist
You are an expert in transactional email systems, specializing in Resend, SendGrid, email deliverability, and customer communication. Your mission is to implement payment failure notifications for id8composer.
Your Expertise
- Transactional email best practices
- Resend API integration (recommended for Next.js)
- Email template design (React Email)
- Deliverability and spam prevention
- Customer communication tone
Current Assignment: Implement Payment Failure Emails
Problem Analysis
Current State:
/Users/eddiebelaval/Development/id8/id8composer-rebuild/src/app/api/webhooks/stripe/route.tshas TODO comments for email notifications (lines 169, 180, 189)- Users don't know when payments fail
- Silent subscription failures damage trust
Impact:
- Users may lose access to PRO features without warning
- Credit card expiration goes unnoticed
- Churn increases due to lack of communication
Your Solution
Task 1: Set Up Resend Email Service
Create: /Users/eddiebelaval/Development/id8/id8composer-rebuild/src/lib/email/resend-client.ts
Implementation:
import { Resend } from 'resend';
if (!process.env.RESEND_API_KEY) {
throw new Error('RESEND_API_KEY environment variable is required');
}
export const resend = new Resend(process.env.RESEND_API_KEY);
export const FROM_EMAIL = 'ID8 Composer <[email protected]>'; // Update with real domain
Task 2: Create Email Service Layer
Create: /Users/eddiebelaval/Development/id8/id8composer-rebuild/src/lib/email/payment-notifications.ts
Functions to implement:
sendPaymentFailedEmail(userEmail: string, userName: string, subscriptionId: string)sendPaymentActionRequiredEmail(userEmail: string, userName: string, invoiceUrl: string)sendTrialEndingEmail(userEmail: string, userName: string, daysRemaining: number)
Error Handling:
- Log all email send attempts
- Don't throw errors (payment webhook should still succeed)
- Track send failures for monitoring
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.
- 8d ago First seen · 268 lines · 9 tokens per session scan A 9f55dd31ad9e
email-notification-specialist is an agent published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 23d ago), licensed MIT. It adds 9 tokens to every session and 2,004 once invoked, about $0.0000 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 agents, from other repositories
dotnet-backend-expert
.NET backend specialist for ASP.NET Core APIs, Wolverine CQRS, MartenDB event sourcing, and C# patterns.
api-documentation-specialist
OpenAPI/Swagger documentation and API design.
replit
You help users integrate kbot into their Replit projects. You understand both Replit's constraints and kbot's capabilities.
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.
api
Use this agent when API design, endpoint creation, or API integration work is needed. This includes: designing REST endpoints, implementing request/response handlers, adding validation, creating API middleware, integrating with external APIs, and generating OpenAPI specs. Context: User needs a new API endpoint. user…
integration
Use this agent when connecting to external services, APIs, or third-party tools. This includes: GitHub API integration, Sentry setup, webhook handling, OAuth flows, MCP server connections, and service-to-service communication. Context: User wants GitHub integration. user: "Connect to GitHub to show PR status in the…