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/dilolabs/nosia/mailer-patternsnpx skills add dilolabs/nosia --skill mailer-patternsgit clone --depth 1 https://github.com/dilolabs/nosiaWrote 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/dilolabs/nosia/mailer-patterns)<a href="https://agentmods.dev/skills/dilolabs/nosia/mailer-patterns"><img src="https://agentmods.dev/badge/skills/dilolabs/nosia/mailer-patterns.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.00070 | $0.02518 |
| Opus 5 | $0.00035 | $0.01259 |
| Sonnet 5 | $0.00014 | $0.00504 |
| Haiku 4.5 | $0.00007 | $0.00252 |
Grade A, and why
mailer-patterns 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 4d 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.
This is a copy
100% identical to mailer-patterns — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mailer Patterns
Philosophy: Minimal Mailers, Bundled Notifications
- Plain-text first, minimal HTML styling with inline CSS
- Bundle notifications instead of sending one email per event
- Transactional emails only (no marketing campaigns)
deliver_laterfor individual emails;deliver_nowis acceptable inside background jobs that already run asynchronously (e.g., digest delivery jobs)- Email previews for development
- No email service abstraction layers (use Action Mailer directly)
Project Knowledge
Stack: Action Mailer (built-in), Solid Queue for background delivery, email previews in development, plain text + HTML multipart emails.
Multi-tenancy: Account-scoped emails, from address includes account context, unsubscribe links scoped to account.
Commands:
rails generate mailer Comment mentioned # Generate mailer
rails generate mailer Digest daily_activity # With methods
# Visit http://localhost:3000/rails/mailers # Preview emails
Pattern 1: Simple Transactional Mailers
# app/mailers/application_mailer.rb
class ApplicationMailer < ActionMailer::Base
default from: ENV.fetch("MAILER_FROM_ADDRESS", "Fizzy <[email protected]>")
layout "mailer"
end
# app/mailers/comment_mailer.rb
class CommentMailer < ApplicationMailer
def mentioned(mention)
@mention = mention
@comment = mention.comment
@card = mention.comment.card
@account = mention.account
mail(
to: mention.user.email,
subject: "#{mention.creator.name} mentioned you in #{@card.title}"
)
end
def new_comment(comment, recipient)
@comment = comment
@card = comment.card
@account = comment.account
mail(
to: recipient.email,
subject: "New comment on #{@card.title}"
)
end
end
# app/mailers/membership_mailer.rb
class MembershipMailer < ApplicationMailer
def invitation(membership)
@membership = membership
@account = membership.account
@inviter = membership.inviter
mail(
to: membership.user.email,
subject: "#{@inviter.name} invited you to #{@account.name}"
)
end
end
# app/mailers/card_mailer.rb
class CardMailer < ApplicationMailer
def assigned(assignment)
@assignment = assignment
@card = assignment.card
@account = assignment.account
mail(
to: assignment.user.email,
subject: "#{assignment.assigner.name} assigned you to #{@card.title}"
)
end
end
What ships with it
2 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.
- 4d ago First seen · 371 lines · 70 tokens per session scan A 219571022832
mailer-patterns is a skill published in the GitHub repository dilolabs/nosia (212 stars, last pushed 26d ago), licensed MIT. It adds 70 tokens to every session and 2,518 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to mailer-patterns, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
facts-discover
Scan the codebase and classify every fact by lifecycle stage — tag @draft, @spec, or @implemented based on what the code actually shows. Add missing facts, fix inaccurate ones, remove obsolete ones. Use when asked to discover facts, bootstrap or update a fact sheet, scan the codebase for truths, sync facts to match…
anneal
Use when the user wants to systematically fix AI code slop — duplicated logic, over-engineering, silent error swallowing, convention drift, cargo-cult patterns, and other LLM-introduced architectural decay — over a specified duration.
new-service
Add a new service to Harbor — scaffold the compose config, environment variables, metadata, documentation, and cross-service integrations. Use this skill whenever the user wants to add a new service to Harbor, integrate a new tool/app/model server, create a compose configuration for a new project, or onboard any…
harbor
CLI toolkit for managing containerized LLM services. Use when the user wants to start, stop, configure, or manage AI/LLM services like Ollama, Open WebUI, llama.cpp, vLLM, LiteLLM, ComfyUI, and 250+ others. Triggers on requests to "run a model", "start ollama", "set up an LLM", "configure harbor", "manage services"…
bughunt
Fully autonomous bug hunting pipeline — discover bugs in a scoped area using parallel subagents, independently triage each finding, fix confirmed issues with subagents, then audit all fixes against repo constraints and target platforms. Runs end-to-end without user interaction.
ideate
Timeboxed ideation on a topic using propose-and-critique subagent pairs. Use when the user wants to brainstorm, explore ideas, discover features, generate options, or think through possibilities for a specified duration. Triggers on requests like "brainstorm X for 30 minutes", "ideate on X", "spend an hour thinking…