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/filipebraida/adonisjs-starter-kit/mailnpx skills add filipebraida/adonisjs-starter-kit --skill mailgit clone --depth 1 https://github.com/filipebraida/adonisjs-starter-kitWrote 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/filipebraida/adonisjs-starter-kit/mail)<a href="https://agentmods.dev/skills/filipebraida/adonisjs-starter-kit/mail"><img src="https://agentmods.dev/badge/skills/filipebraida/adonisjs-starter-kit/mail.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.00107 | $0.01839 |
| Opus 5 | $0.00053 | $0.00920 |
| Sonnet 5 | $0.00021 | $0.00368 |
| Haiku 4.5 | $0.00011 | $0.00184 |
Grade A, and why
mail 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 5d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Emails are classes that extend @adonisjs/mail's BaseMail. The prepare() method sets recipients, subject, and calls this.message.htmlView('<mod>::emails/<template>', {...}). Templates are .edge files at app/<mod>/ui/emails/<name>.edge that consume a shared @email.layout component. The layout owns fonts, colors, button styles, header, and footer; each template only fills the body slot. Raw <html><head><style> blocks are never authored — MJML with the shared layout is mandatory. Emails are always dispatched from event listeners, not from actions directly (see [[actions-events]]), so unit tests can fake the emitter and end-to-end tests can fake the mail transport.
Rules
- Mail class location:
app/<mod>/mails/<name>_notification.ts— one file per email. - Class shape: extends
BaseMail, declaresfrom = env.get('EMAIL_FROM'), setssubjecteither as a class field or dynamically inprepare()from atranslationsfield. prepare()does all the work: build any URL (viasignedUrlForfor time-limited links), callthis.message.to(recipient).subject(...), then render withhtmlView('<mod>::emails/<template>', props). Always spread...mailContext()into props so the layout hasappName+appUrl.- Templates live at
app/<mod>/ui/emails/<name>.edge. Every template opens with@email.layout({ title, preview: subtitle })and closes with@end. Between them, only<mj-section>markup — body, button, text. - Shared MJML layout is the single source of truth for typography, colors, header, footer. Change once, all emails update.
mailContext()returns{ appName, appUrl }from env with a fallback name. Every mail class spreads it intohtmlViewprops so the layout can render brand chrome.- Env:
EMAIL_FROMrequired;APP_NAMEoptional (has a fallback);APP_URLrequired. SMTP vars for local dev (typically Mailpit) and the prod driver's API key (e.g.RESEND_API_KEY). - i18n: the translation shape is a plain interface (
subject,title,subtitle,actionBtn,defaultMessage). Passed from the caller. Keys live per module underemails.<name>.*in the locale JSON — see [[i18n]].
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.
- 5d ago First seen · 128 lines · 107 tokens per session scan A b85891001d7b
mail is a skill published in the GitHub repository filipebraida/adonisjs-starter-kit (95 stars, last pushed 25d ago), licensed MIT. It adds 107 tokens to every session and 1,839 once invoked, about $0.0005 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
coss-particles
Index of all COSS UI particle examples. Use when implementing UI features to find copy-paste-ready component patterns built on coss primitives. Each particle has a description and a JSON URL for easy installation.
coss
Helps implement coss UI components correctly. Use when building UIs with coss primitives and patterns (buttons, dialogs, selects, forms, menus, tabs, segmented controls, inputs, toasts, etc.), migrating from shadcn/Radix to coss/Base UI, composing trigger-based overlays, or troubleshooting coss component behavior.…
ui-beats
Use this skill when users want to add, customize, or troubleshoot UI Beats components in React/Next.js projects. It covers component selection, shadcn registry installation from uibeats.com, the UI Beats MCP server, motion and reduced-motion handling, and integration patterns for animated sections.
morphous-catalog
Create or refresh Morphous website design-system/theme bundles from animal, insect, plant, landscape, mineral, weather, or other nature motifs. Use when Codex is asked to generate Morphous motif images, light/dark design-system boards, reusable image prompts, generated web assets, shadcn/tweakcn theme exports, or the…
ktui
Comprehensive guide to KtUI (Keenthemes Tailwind UI) — components, theming, initialization, data-attribute API, event system, helpers, and common patterns. Use this skill when building UI with KtUI, adding/customizing components, working with KtUI theming/colors/dark-mode, or when the user mentions KtUI, ktui…
ktui-datatable
KtUI DataTable (KTDataTable) — local/remote data, sorting, filtering, pagination, checkbox selection, state persistence, fixed layouts, event system, and architecture. Use this skill when building, debugging, or customizing DataTable components.