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 instructions/veliovgroup/mail-time/agents-mdgit clone --depth 1 https://github.com/veliovgroup/mail-timeWhat 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.03628 | $0.03628 |
| Opus 5 | $0.01814 | $0.01814 |
| Sonnet 5 | $0.00726 | $0.00726 |
| Haiku 4.5 | $0.00363 | $0.00363 |
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.
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
MailTimeper email class when policies differ (otp,transactional,marketing, …): own options; ownprefixonly when purpose/settings differ. prefixsame for allclient+serveron one logical queue (app enqueuesprefix: 'otp', mail worker drainsprefix: 'otp').- Never same
prefixon 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
serverinstances on one machine (~1 per CPU core) for parallel drains across prefixes, not duplicate drains of sameprefix. - Same
prefixcluster-wide = one JoSk lease tick at a time → extra pods ≠ N× throughput, but do buy failover/HA (warm standby with a differentlockOwnerIdtakes the lease the next tick if the winner dies). - High volume one queue → shard prefixes (
marketing-0, …), not duplicate instances sameprefix.
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 |
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.
- 2d ago First seen · 199 lines · 3,628 tokens per session scan A 4ce9747d3a4e
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.
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.
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.
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.
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).
better-email-mcp CLAUDE.md
Instructions for n24q02m/better-email-mcp, covering claude.md - better-email-mcp, commands, setup, lint & type check and fix.
SoDam-WikiMate AGENTS.md
Instructions for sodam-ai/SoDam-WikiMate, covering wikimate 작업 규칙 (크로스툴 — claude code · codex · gemini 공용), 문체, 자동 동작 (자연어 트리거 — 강제 호출 불필요), 접근 규칙 (자동 감지 — 특정 도구에 한정하지 않음) and obsidian 규칙.