What is mail-time AGENTS.md?

Project instructions for mail-time, an email queue and sender for Node.js and Bun applications running across multiple servers. It uses shared storage such as Redis, MongoDB, or PostgreSQL so separate processes can coordinate email work.

They help configure queues for different email classes such as one-time passwords, transactional messages, and marketing mail, including multiple sender processes on one or more machines.

They explain how to separate applications that add emails from servers that send them, and how to avoid mixing queues with different email policies.

How veliovgroup/mail-time configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to veliovgroup/mail-time. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/veliovgroup/mail-time/master/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/veliovgroup/mail-time

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/veliovgroup/mail-time/agents-md/github.svg)](https://agentmods.dev/instructions/veliovgroup/mail-time/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/veliovgroup/mail-time/agents-md"><img src="https://agentmods.dev/badge/instructions/veliovgroup/mail-time/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/veliovgroup/mail-time/agents-md"><img src="https://agentmods.dev/badge/instructions/veliovgroup/mail-time/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 4,148 This file is loaded in full into every session.

When invoked 4,148 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.04148	$0.04148
Opus 5.5	$0.01659	$0.01659
Sonnet 5.5	$0.00830	$0.00830
Haiku 4.5	$0.00415	$0.00415

Measured 1mo ago against content hash 1434140c29e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mail-time AGENTS.md 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.

AGENTS.md · 211 lines

How it starts

The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

mail-time NPM library. Email queue + sender for horizontally scaled Node.js & Bun apps. Synchronizes the queue across processes via Redis / MongoDB / PostgreSQL / custom adapter. Built on top of josk for scheduling and task management, and nodemailer for email transport management.

Mission

Send and queue emails in horizontally scaled Node.js and Bun.js. Bulletproof. High perf. Storage agnostic. Two roles: server (drains + sends) and client (enqueues). Many clients + many servers behind one prefix.

Topology / tuning (read README for use-cases)

Multiple instances — encouraged

One MailTime per email class when policies differ (otp, transactional, marketing, …): own options; own prefix only when purpose/settings differ.
prefix same for all client + server on one logical queue (app enqueues prefix: 'otp', mail worker drains prefix: 'otp').
Never same prefix on two instances with different mail policy (concat, retries, etc.).
App pods: type: 'client'. Mail VM: type: 'server' (systemd: one unit per class, e.g. mailtime@otp).

One mail host: 2–8 servers

Run 2–8 server instances on one machine (~1 per CPU core) for parallel drains across prefixes, not duplicate drains of same prefix.
Same prefix cluster-wide = one JoSk lease tick at a time → extra pods ≠ N× throughput, but do buy failover/HA. JoSk 6.4+ preserves claimed interval runs on restart: graceful destroy({ drain: true }) hands back unfinished scans; an unclean death can delay the next scan until josk.zombieTime.
High volume one queue → shard prefixes (marketing-0, …), not duplicate instances same prefix.

Throughput levers

Lever	Effect
More `prefix`es / instances	More parallel drain loops
`revolvingInterval` ↓, `josk.min/maxRevolvingDelay` ↓	Faster pickup, more storage I/O
Dedicated mail workers	SMTP + tuning isolated from app
`concurrency: N` (MailTime)	N parallel SMTPs per server within a single instance
`mode: 'one'` (MailTime)	One row claimed per tick — fairness across nodes; storage CAS prevents dupes
`josk.concurrency: 1`	No overlapping `iterate` on one process

Read the full file on GitHub · 211 lines

Changes

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 Changed · +2 lines · +64 tokens per session 1434140c29e9
1mo ago Changed · +10 lines · +392 tokens per session a0a9ffabfa28
1mo ago Changed · +64 tokens per session 78f4d6a1781a
2mo ago First seen · 199 lines · 3,628 tokens per session scan A 4ce9747d3a4e

Subscribe to this mod's changes

mail-time AGENTS.md is an instructions file published in the GitHub repository veliovgroup/mail-time (143 stars, last pushed 9d ago), licensed BSD-3-Clause. It adds 4,148 tokens to every session, about $0.0166 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-30.

mail mailer nodejs npm server smtp

mail-time AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
mail-time AGENTS.mdveliovgroup/mail-time	Instructions file	143	9d ago	BSD-3-Clause	A	4,148	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

mail-time: Instructions file for Codex