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.

In plain words
What is it for?
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.
Why use it?
They explain how to separate applications that add emails from servers that send them, and how to avoid mixing queues with different email policies.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/veliovgroup/mail-time/agents-md
Clone the repo
git clone --depth 1 https://github.com/veliovgroup/mail-time

Made for: Codex, OpenCode.

Per session 3,628 This file is loaded in full into every session.
When invoked 3,628 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.03628 $0.03628
Opus 5 $0.01814 $0.01814
Sonnet 5 $0.00726 $0.00726
Haiku 4.5 $0.00363 $0.00363

Measured 2d ago against content hash 4ce9747d3a4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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 · 199 lines

How it starts

The opening of the file, as written. The whole thing — 199 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 (warm standby with a different lockOwnerId takes the lease the next tick if the winner dies).
  • High volume one queue → shard prefixes (marketing-0, …), not duplicate instances same prefix.

Throughput levers

Lever Effect
More prefixes / 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 · 199 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.

  1. 2d 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 19d ago), licensed BSD-3-Clause. It adds 3,628 tokens to every session, about $0.0181 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.

Related

Other instructions, from other repositories

claude-skill-antivirus copilot-instructions.md

Instructions for claude-world/claude-skill-antivirus: This is a JavaScript security scanner for Claude Code Skills. It has 9 detection engines. Security is critical — never bypass checks, validate all input.

claude-world/claude-skill-antivirus · 31 tokens

huly-mcp CLAUDE.md

Instructions for dearlordylord/huly-mcp, covering project instructions, design principle: llm-first api, project harness (copy to new projects), package manager and verification.

dearlordylord/huly-mcp · 3,317 tokens

zapo CLAUDE.md

Instructions for vinikjkkj/zapo: The contributor handbook for this repository lives in AGENTS.md. Read that file and follow it as your primary source of project conventions, architecture rules, performance constraints, and review anti-patterns.

vinikjkkj/zapo · 152 tokens

Silex AGENTS.md

AGENTS.md instructions for silexlabs/Silex, covering agents.md, tech stack, run it locally, building the desktop app and when writing code for silex (editing source).

silexlabs/Silex · 1,155 tokens

better-email-mcp CLAUDE.md

Instructions for n24q02m/better-email-mcp, covering claude.md - better-email-mcp, commands, setup, lint & type check and fix.

n24q02m/better-email-mcp · 2,457 tokens

SoDam-WikiMate AGENTS.md

Instructions for sodam-ai/SoDam-WikiMate, covering wikimate 작업 규칙 (크로스툴 — claude code · codex · gemini 공용), 문체, 자동 동작 (자연어 트리거 — 강제 호출 불필요), 접근 규칙 (자동 감지 — 특정 도구에 한정하지 않음) and obsidian 규칙.

sodam-ai/SoDam-WikiMate · 1,936 tokens